<html><body><br />
Folks, I have been using FoxtrotGPS going back to Tango. And now Joshua has fixed something in a few days that has annoyed me for years ! So, its way past time I did something to help. I have not called myself a programmer for maybe, 15 years so most unsafe there but I do know about documentation !<br /><br /><a href="https://launchpad.net/~t-bubeck" class="sprite person">Dr. Tilmann Bubeck</a> <span title="2012-08-11 00:56:24 EST">suggested </span>ASCIIdoc (<a href="http://www.methods.co.nz/asciidoc/">http://www.methods.co.nz/asciidoc/</a>) might be a good tool (bug #1035343). I have not used it but I have been in a project that decided to use Docbook, the developers hated it and documentation more or less froze and we all know that that meant ! But Tilman is right, FoxtrotGPS is good enough to deserve better documentaion and any doc solution needs to be one source, lots of output formats. <br /><br />Coming as I do from a Systems Admin background, there is nothing worse than a command line tool with no man page (maybe an info page is worse!) but I don't see man pages useful for a GUI app. I reckon FoxtrotGPS needs some HTML pages on the website and a nicely formated PDF attached to the tarballs.<br /><br />If it sounds like there is some interest in this approach, I am willing to have a go at drafting up something in asciidoc so we can have a play with it and see if it works for the FoxtrotGPS developers. Thoughts ?<br /><br />David<br /></body></html>