DTDs for Internal IT Documents?
Saqib Ali asks: "A DTD (Documentation Type Definition) defines the document structure with a list of legal elements. DocBook DTD is being widely used in creating Linux related documentation. However I am looking for a XML DTD that is more suited to internal IT documentation, and easy to learn and use. Preferably I would like to use a DTD that can be used with OpenOffice. What DTDs are other Slashdot readers using for for internal IT documentation? I have created documentation using DocBook DTD and hosted them on a Apache Cocoon . Cocoon lets me transform the XML to HTML or PDF. I would like to keep the same backend infrastructure (i.e. Cocoon) but try out other DTDs that are suited for IT related documentation. Any ideas?"
Is there some reason why Docbook is insuffient? More info at www.docbook.org.
-molo
Using your sig line to advertise for friends is lame.
Use ReST (ReStructured Text) and DocUtils. DocUtils outputs perfectly nice XML (ignore the HTML, LaTeX, and other options). It's then easy enough to use XSL:FO and FOP/XEP to transform the XML to PDF.
Been using it for a year, and I'm absolutely flippin' delighted with it. Structured documentation that's both open-standard and imminently readable, yet delivers great PDFs.
--
Don't like it? Respond with words, not karma.
Structure Documents. Structure Documents has it is own benefits:
# "Write Once, Publish Anywhere" - You have only to prepare single documents; you can either use them as they are with stylesheets or convert them later to different physical media and formats, including plain text, XHTML and PDF.
# Since your documents are in non-proprietary text format, you can edit them with any text editor, and assure their continuity and cross-platform compatibilty.
# The physical layout of documents is separated from the content.
# Retrieving specific information is very esay from structured document.
Consensus is good, but informed dictatorship is better