Slashdot Mirror

← Back to Stories (view on slashdot.org)

DTDs for Internal IT Documents?

Posted by Cliff on from the defining-your-documents dept.

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?"

2 of 44 comments (clear)

  1. Why not Docbook? by molo · · Score: 4, Interesting

    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.
  2. Skip XML for source. by FFFish · · Score: 4, Interesting

    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.