On Sun, 2003-03-16 at 12:19, Chris K Chew wrote: > > From: Quinton McCombs [mailto:[EMAIL PROTECTED] > > > > I am all for changing the format for documentation. I have never looked > > at the docbook format. I guess I will take a look at it. I would like > > a format that can be rendered to PDF as well. I would like to see the > > user manual available in PDF format. The Avalon project has a nice > > manual in PDf format. It just seems to give the project a more > > "finished" appearance... Amazing what little things like that can do. > > Hello. > > You have probably noticed the conversation I inadvertently started on > turbine-user by mentioning docbook in my reply to Jeff Linwood's "Turbine > Concepts" thread where he offers to contribute his article. > > Henning, I appreciated your response to his thoughts, as I had thought many > of the same things but was unsure of writing them. Thank you. > > However, Jason makes two good points that I should keep in mind as I try and > lead this effort. First, content should be the focus over and above the > mechanism. Second, there are standards in the Apache Jakarta world that > should be respected.
All I'm asking for is a reasonable approach. I would never try to road block an effort to write documentation, you go crazy. I'm glad you agree that content should be the focus, to me that seems the most reasonable approach. As long as everything is in the same XML format you can at a future point in time move to a different format or augment the existing format. There are certainly limitations with the anakia format. About two years ago I started a contract with Addison-Wellsley for a Turbine book and tried to use the anakia format and it can be limiting when trying to render PDFs with exacting typographic control but I think in most cases this really isn't an issue. Ultimately I'm not going to stop any effort here, documentation or otherwise. To that end I would even suggest that the separate repositories be run as separate projects if that is desired. If there are a group of you trying to improve Turbine 2.x code-wise, documentation-wise then go for it. I won't vote on anything related to the 2.x codebase, or anything in a 2.x repository. As I would like to setup a repository to start anew an attempt at what a group of us see as the future of Turbine. Namely clean separation of concerns, the clean use of Avalon and a Maven-based build system and TDK using the Summit and Plexus plugins. -- jvz. Jason van Zyl [EMAIL PROTECTED] http://tambora.zenplex.org In short, man creates for himself a new religion of a rational and technical order to justify his work and to be justified in it. -- Jacques Ellul, The Technological Society --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
