On 12/9/05, <b class="gmail_sendername">Scot Jenkins</b> <<a href="mailto:scotjenkins@gmail.com">scotjenkins@gmail.com</a>> wrote:<div><span class="gmail_quote"></span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Where I'm working, we're using a combination of DocBook [1] and<br>Subversion[2] (for version control). It's a bit of a complicated<br>initial setup but for a larger project with multiple folks<br>creating/editing documentation, I think it's the best route to go. We
<br>use XMLmind[3] as an editor (Windows and UNIX versions available) to<br>create the DocBook source. XMLmind really makes creating the XML<br>source easy. The nice part about having a document as docbook source<br>is that you can generate whatever format you need (txt, html, pdf,
<br>etc...)<br><br>[1] <a href="http://www.docbook.org/">http://www.docbook.org/</a><br>[2] <a href="http://subversion.tigris.org/">http://subversion.tigris.org/</a><br>[3] <a href="http://www.xmlmind.com/xmleditor/">http://www.xmlmind.com/xmleditor/
</a></blockquote><div><br>
<br>
I think docbook is a good option with a lot of flexibility and as
you pointed out we can use it with our current subversion setup that we
use to handle our code.<br>
<br>
Did you create your own software to handle publishing it on the web?<br>
</div><br></div>I think I'll look into OpenOffice as a DocBook editor. There has been some progress on this <a href="http://www.indesko.com/sites/en/downloads/ooo2dbk/view">plug-in</a> [<a href="http://indesk.com">indesk.com
</a>] that may make it a viable solution.<br>