Daniel, comments below:<br><pre><br>> Well, I'm not the one maintaining the manual, but my initial idea was to <br>> have it in a format that can be published on the web *and* converted to <br>> a downloadable PDF format. I thought it could have been written in the <br>
> same ReStructuredText format as the rest of our docs and converted and <br>> packaged into a downloadable PDF using some ReST tools.<br><br>The manual is coming along nice. (about 40 pages, with appendices 100)<br>
<br>I would love a magical script to produce the appendices. It would be nice if I could call a script to convert specific website docs into nice formatted text for my document.<br><br><br>> The drawback of .odt files (or any word processor files) is that you <br>
> cannot easily track changes between revisions in SVN and cannot easily <br>> merge changes if multiple people work on the same doc. It's just a <br>> binary blob that is committed to the repository.<br><br>
I am aware of that. I was just looking to back of my work, or maybe someone might have wanted to see my progress, or add a section etc...no worries man. In the end I'll just upload the pdf to the site.<br><br>> Just an opinion. I wonder what others think.<br>
<br>Maybe I can continue my work on the manual, for a 1.0 release of it, and then all of your additions can be made for 2.0 ? <br><br>-jeff<br><br></pre>