Shawn: > >Where do the stylesheets come from? I could try coming up with them myself > >but you'll likely get a better job from someone else. I would just use a > >wyswyg editor (trial version haha). > Richard: > I can do the style sheets for both the html and the fop, I've got a lot of > experience now with fop.
(Sigh). Some months ago I asked for the stylesheet to create HTML from taglib_docu.xml on the list. I was sure something like that must exist! Did not get an answer. Now that I have written a version myself and also one for PDF, I am surrounded by people who offer to do that ;) This is what has to be done if someone want to transfer docs to docbook: 1) Agree on which version of docbook shall be used. Setup a documentation page telling developers where to find documentation about it, editors, examples etc. Developers can immediately start then to write docs. Ok, that should be possible.... 2) Integrate all the stuff that is needed to generate various output formats (HTML, PDF) from the sources. Ok, that should be already there somewhere: Stylesheets for docbook... Must just be found and integrated somehow... 3) User Guide: Transfer Userguide into xml format. Here we would be lost without your knowledge, Richard. 4) Reference Part: We currently have a reference part within the manual, and we have reference documentation within taglib_docu.xml. The problem is not to transfer the xml file to anything, the problem is to merge these two. The taglib_docu.xml is (must be) always up to date, developers have to edit it to integrate new tags and attributes. But the manual contains useful information that is not within xml file. I would think we should keep the simple structure of the xml file, but allowing docbook tags to be nested within summary and info tags. This way it would be easily possible to transfer it into pure docbook. Currently a subset of HTML is used within those comment tags, but it will not be a problem to switch to docbook tags, it is already xml. The problem is to merge these two and I'm in doubt it can be automatically be done. Lot's of information is redundant within both. 5) Generate new stylesheet to generate docbook from taglib_docu.xml. The result then can be easily integrated within user guide to be transformed into anything you like. Easy again. Well, that is really a lot of work to do. Isn't that too much work for a project where no one yet has volunteered to start and maintain a FAQ for the project? Regards Dirk ------------------------------------------------------- This SF.net email is sponsored by: ApacheCon, November 18-21 in Las Vegas (supported by COMDEX), the only Apache event to be fully supported by the ASF. http://www.apachecon.com _______________________________________________ DbForms Mailing List http://www.wap-force.net/dbforms
