So which is better, PDF or ePub? That depends on what you want to do with it. If you format a PDF with the page size of the device you're going to read it on, then it looks great. But if you read an PDF formatted for A4 pages on an 6" eBook reader screen, it looks a mess. Yes, some readers do enable the PDF to be reflowed, but this is never entirely successful. Also, on my Sony Reader, if I increase the font size, the page flow gets messed up.

ePub, on the other hand, is designed to be reflowed. I find that at the default font size, there is not much difference between ePub and PDF on my Sony Reader. But if you increase the font size, the ePub version handles it much, much better. So I've switched to using ePub as the main version I read.

Where ePub really comes into it's own is on even smaller devices, such as iPhone/iPod Touch. I previously used GoodReader to read the iPod version of the PDF. This worked quite well. I tried Stanza, but never really liked it for reading PDFs. But it's a much better ePub reader, so I've switched to using Stanza/ePub on my iPod.

I said in the release notes that support for ePub in SmallNews is experimental. I have found that articles from The Guardian work very well in this format. But some other feeds are a little more unpredictable. ePub is an XHTML-based format, so the HTML from the newspaper site has to be converted to XHTML. If the source material is not well-constructed, this can cause problems. Most feeds I have tried do work, but my Sony Reader has crashed on 2 or 3 occasions. Whether this is the fault of the Sony software or the ePub created by SmallNews, I don't know. Anyway, I would argue that even if the ePub is not quite perfect, the Sony Reader still shouldn't crash. I will watch this over the next few weeks and see if I can establish any pattern.

If you're interested in the technical detail of creating ePub files, they are basically a zip file of XHTML content, XML metadata and images. I found three tutorials about very useful:

• http://www.hxa.name/articles/content/epub-guide_hxa7241_2007.html
• http://www.jedisaber.com/eBooks/tutorial.asp
• http://www.spontaneousderivation.com/2008/12/13/creating-ebooks-an-epub-tutorial/

• Purging of the database. This can be performed manually from the Settings tab, and you can specify how many days of articles you want to keep.
  
• Experimental ePub support. You can now specify that an ePub version of the newspaper is created either as well or instead of the PDF version. It works very well for The Guardian, but can be a little more unpredictable for other feeds. More information about that to follow.
  
• Wait for publication. The handler for the The Guardian has the (as yet, undocumented) ability to generate the newspaper in the same order as the printed version. This makes it a great deal more coherent, but The Guardian don't always get around to publishing this until mid-morning. This option can instruct SmallNews to wait until today's edition has been published before starting a scheduled run. More info to follow on that too.
  

All of these need a bit more documentation, which I will aim to do shortly. I have added quite a bit of extra documentation since 2.0b3; you can find it on the SmallNews page.

Also, the source code for SmallNews is now available. It has always been an open source application in principle, I just never got round to publishing the source.

• Scheduled daily creation of the newspaper
  
• Create PDFs of articles from the database
  
• Send PDFs of articles from the database by e-mail
  
• A feed tester, to allow individual feeds to be tried (useful if they are not behaving the way you expect)
  
• A fix to one of The Guardian handlers which was not writing articles to the database correctly

I've also written some more documentation, and will continue to add to this over the next week.

The one outstanding feature that needs to be added before I call this version 2.0 is the ability to purge the database of old articles.

After this, I am planning to add two new significant features:

• Ability to search the database by keyword, author, date, etc, instead of just the article id.
  
• Support for the Apple iPad. This looks to me like it's going to be a great device to use SmallNews on, but I'll have to wait and see what the best format will be. I understand that it will support the ePub format, so I may look again at that. I originally consider ePub when adding support for the Sony Reader, but decided that a small-page PDF worked very well, so it wasn't really necessary.

You can now:

• specify the colour of the buttons, labels, and the highlight and select colours used when navigating the DVD
• choose to use a solid colour as the background instead of an image file
• choose whether the buttons should have borders (I always thought this was necessary, but turns out they weren’t).

I’ve also improved (I hope) the logic about which menu settings get saved in the template.

There is known problem when selected dark coloured labels on a dark image background. The button borders show up, but the text doesn’t. I think this is a bug/oddity in iMagine Photo which is used to create the menus. If you use a solid background, or lighter colours, it’s OK.

SmallDVD 2.3 is available for download. This release adds the ability to create DVDs without menus and optionally play the videos in a loop. There is also an updated version of ffmpeg, and a change to the way MPEG2 files are handled.

A new DVD settings tab has been added, which allows you to specify whether the DVD should be created with a menu or not (by default, a menu is created). If you put several videos on a menuless DVD, they will play in sequence. If the DVD has no menu, you can specify whether the videos should play in a continuous loop. Also, the aspect, format and chapter settings have been moved from the DVD menu tab to the DVD settings tab.

This release also makes two changes to the way ffmpeg is used. The short reason for this is to improve the compatibility with MPEG2 input videos.

If you're interested in the long explanation, first, a word of explanation. ffmpeg is the fabulous video conversion command line utility which SmallDVD uses for converting and remultiplexing video files ready for placed on a DVD. It is constantly evolving, supporting more file formats. As ffmpeg doesn't have formal releases, it is typically built from source code using all the latest enhancements submitted. But it appears that "latest" is not always "greatest".

All versions of SmallDVD up to and including 2.0 used a version of ffmpeg I compiled back in March 2007. For SmallDVD 2.1 (and subsequently 2.2), I compiled a new version to enable a wider variety of files to be accepted by SmallDVD. However, this later version had two problems:

• Videos saved from MPEGStreamClip as "MPEG2 with MP2 audio" were no longer accepted by SmallDVD.
  
• In some cases, chapter marks were not being inserted correctly in MPEG2 videos.

The first of these problems was an ffmpeg bug, which was fixed by building a newer version. However, this still showed the second problem. Therefore, while I have included a new version of ffmpeg (r21020) in SmallDVD 2.3, I have also reinstated the original version I was using (r8320) up until SmallDVD 2.0.

So, in SmallDVD 2.3, MPEG2 input video which does not require conversion will use the old ffmpeg. All other video which does require conversion will use the new ffmpeg (this includes MPEG2 files you have explicitly set to be converted).

The end result, hopefully, will be better compatibility with as many types of files as possible. Ideally, I would like to use just one ffmpeg, but until I can get the new version working as reliably on MPEG2 files as the old version did, I will retain both.

In the short term, the workaround is to save from MPEGStreamClip using "Convert to TS with MP2 audio". But I will look into why it's not working with the standard format saved by MPEGStreamClip.
Alternatively, you could revert to SmallDVD 2.0.

I use the combination of MPEGStreamClip + SmallDVD a lot, so am highly motivated to fix this!

Since then, I've had a lot of requests for greater control over the DVD menus and burning the image to DVD. I was initially resistant to these as I felt that this was really iDVD's domain - if you want quick and easy DVD authoring, use SmallDVD; if you want fancy menus, use iDVD. But I have now been convinced by a couple of people that the simplicity of SmallDVD can be retained while adding more flexibility to the menus, and that it would continue to serve a purpose that iDVD does not.

So I am planning a number of 2.x releases to incrementally enhance the menu functionality.

• 2.2 has been released today. It adds more control over font selection, and allows additional text to be added to the menu.
• 2.3 will (probably) add the option of creating DVDs without menus.
• 2.4 will (probably) give greater control over the background of the menu, and maybe the button and text colours.

Additionally, the documentation is getting a long way out of date, and needs a significant update.

However, the current AppleScript code for SmallDVD is becoming increasingly hard to maintain. What started as 100 fairly elegant lines of AppleScript has now becoming a rather more unwieldy 1300+ lines that has been added to regularly over the last 4 years. At the start, AppleScript seemed like a nice, easy way of creating a simple user interface to the command line tools that do all the hard work in SmallDVD. But it's not a great way of building larger applications. Also, from Mac OS X 10.6, Apple seem to have deprecated the AppleScript Studio part of the development tools, encouraging greater use of Objective C. This is a pity in many ways, and not a very developer-friendly thing to do. However, there's no doubt that SmallDVD's code needs an overhaul, so it makes sense to convert it to Objective C.

So, in parallel with the 2.x releases, I am going to start work on SmallDVD 3.0, which will be a complete rewrite in Objective C. The initial releases will almost certainly have less functionality than the latest 2.x version, but over time it should catch up and overtake. It should also provide a more sustainable basis for future enhancement.

The priority with SmallDVD 3.0 will continue to be keeping it as simple as possible. If a feature would require too much complexity in the user interface, it probably won't get in.

As always, all suggestions very gratefully received. The forums on Get Satisfaction are the best way to submit feedback, but you can also e-mail me directly.