Having read some ideas about Help and documention in this forum, I would definitely NOT advise using PDF format for the main mAirList help file–though it is excellent for a printed manual. Acrobat (now Adobe) Reader pre-loads a large number of large DLLs into memory at system startup and I would not recommend even installing Adobe Reader on any PC you plan to use for playout.
The best of all would of course be a real CHM Help File, but I don’t suppose–since Torben seems to be one of those “anti-Microsoft” people–that he would allow us to create one?
Remember that everyone with a Microsoft PC has the Help Viewer installed and can therefore read a CHM file immediately, but not everyone has Acrobat Reader installed on their PC!
The manual is written in DocBook/XML, so it can be converted to any format you like By now, I offer the HTML pages found on http://www.mairlist.com/documentation/ (either as a single page or a set of smaller pages). These files are not yet included in the distribution ZIP file, but they will be, as soon as mAirList 2.0 is ready.
CHM is an excellent idea, and there are tools to convert DocBook to CHM. However, you guessed it g, I haven’t found a Linux tool for that yet. It’s not that I’m such a big Microsoft hater, but I have automated the build/package/upload process with a couple of scripts on my Linux box. Generating CHM can’t be automated at the moment. Once we have a stable mAirList 2.0 release, I would of course manually generate a CHM file, but for now, I would not want this any time I change a single line in the manual (and, as you know, I’m still working on it every now and then, so this happens quite often).
By now, I offer the HTML pages found on