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
---
Peter Åstrand ThinLinc Chief Developer
Cendio AB http://www.cendio.com
Wallenbergs gata 4
583 30 Linköping Phone: +46-13-21 46 00
------------------------------------------------------------------------------
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
