Hello Tony! Great that you are so enthusiastic.
The reason for using a specific version of DocBook is connected to the tools we use to generate the documentation. I suspect that a change in version of DocBook would require an upgrade of the tools. Please go ahead and do so, it sounds like a great improvement of how things are done now. I can think of no reason not to upgrade the version and tools as long as the result is improved. To get a feel of how the documentation is built, check out the argouml project from the subversion repository, enter the documentation directory and build the html and pdf versions (targets defaulthtml and pdf). To build the pdf documentation (using fop) you also need to download a library to handle pictures (for license issues). There are checks and comments in the build.xml to help you through this. I hope that you, while finding new and improved tools, can fix so that this toolchain is simplified and improved. I think there is a css files for the generated Cookbook called look-and-feel.css. As you noticed it is overridden by the Tigris default settings. There is however a way to publish files from Tigris without the Tigris look and feel (compare http://argouml-stats.tigris.org/documentation/defaulthtml/cookbook/ and http://argouml-stats.tigris.org/nonav/documentation/defaulthtml/cookbook/). If so, I think it comes into play. /Linus 2007/11/27, Tony Rogers <[EMAIL PROTECTED]>: > > Hey Tom, > > First of all, thanks for your enthusiastic and warm welcome! I must > apologize for the late response; life gone crazy. Things got less > crazy, so I'm back. :) > > I'll take your recommendation and start with bugs and DocBook. I poked > around and found a bug I was interested in > (http://argouml.tigris.org/issues/show_bug.cgi?id=7), subscribed, and > added my two cents. Is that all there is to it? > > Also, I see that the documentation is written in DocBook 4. Is there > any reason DocBook 5 is not being used? If not, I believe I could > convert it without much difficulty. > > Converting would allow many benefits, including standard XML notation, > XML modules (for example, XInclude, rather than having to define > entities for sections of the book), being built on top of existing > standards (e.g. "xml:lang"), and (mercifully!) context-sensitive > elements. For example, because of limitations of DTD, there might be > elements like <articleinfo>, <sectioninfo>, and forth. In DocBook 5 > there is simply <info>, which describes its parent element. Far more > intuitive, consistent, and saves a few keystrokes to boot. :D > > Also, is there a way to create/edit CSS for the Cookbook's HTML ouput? > Or is it pretty much stuck with what Tigris has? > > Quick summary of my questions: > > 1. Is helping out with bugs really that simple? Or is there more? > 2. Any reason against DocBook 5? (If not, can I begin converting?) > 3. Any way to customize CSS for the online Cookbook? > > Thank you muchly! > > -- Zearin > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
