On 03/22/10 09:55, DRC wrote: > I like RST, but it cannot do automatic chapter/section numbering, which > makes it difficult to use for large publications.
It seem unlikely that TigerVNC doc will ever fit that description ! ;) The TOTAL absence of the word documentation on tigervnc.com is rather surprising and off-putting. I would have thought the very minimum would an HTML rendition of the man page. I think the content is more important than the format. man or straight text would probably suffice if the areas I noted were fleshed out a bit. This could be done with minimal pain and time investment. Since it seems no one involved in the project has the heart for more elaborate documenation adding the missing areas to the existing doc and linking it into the project web site would take if from sub-minimal to minimal. I suspect the time invested would be quickly recovered by a drop time explaining things to users. m2c. > > On 3/22/10 3:31 AM, Peter Åstrand wrote: >>>> While we're on the subject of documentation, though ... Assuming we did >>>> develop documentation for TigerVNC, what are some ideas regarding the >>>> preferred markup to use? The TurboVNC and VirtualGL documentation was >>>> written using Deplate, so I assume we'd want to use something a little >>>> more standard for TigerVNC, like maybe Docbook (?) >>>> >>> >>> I've always been partial to good ol' text/plain. :) >>> >>> So if it's sufficient, my vote is for rst. >> >> +1 > > ---------------- ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ Tigervnc-devel mailing list Tigervnc-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/tigervnc-devel
