Slashdot Mirror

← Back to Stories (view on slashdot.org)

Using the DocBook DTD for Internal Documents?

Posted by Cliff on from the going-digital dept.

Saqib Ali asks: "These days, most of the Linux Documentation is created using DocBook DTD. I was wondering if it will be useful for a large Enterprise to create Internal IT documents using DocBook DTD. Any success stories where a large enterprise converted all of its internal IT documentation to DocBook, with management's support? Any other things/issues to keep in mind before embarking on such a mission?"

2 of 58 comments (clear)

  1. I try using XML to structure my docs... by scrytch · · Score: 3, Insightful

    But the structure navigator in every single bloody XML editor I have ever tried, free or commercial, tends to look like this:


    book
    |
    +--chapter
    +--chapter
    | |
    | +--section
    | +--section
    |
    |--chapter
    ad nauseum. Not chapter titles, not section titles, the literal words chapter and section. Multiply this by hundreds of sections.

    How. Completely. Useless.

    Until I can find an XML editor with some bloody sense to its structure navigator, I would rather use word. And no, I don't really want to use a WYSIWYG editor, because I want to know what XML it generates for my custom xslt snippets (which I might add I also have similar problems navigating with these brain dead editors)

    --
    I've finally had it: until slashdot gets article moderation, I am not coming back.
  2. We did it. by Some+guy+named+Chris · · Score: 5, Insightful

    It was a nightmare.

    Anyone who was not a programmer balked at the idea of having to write documentation in a (Gasp!) markup language. "Just give me Word!" they would whine.

    There is a lot of overhead associated with DocBook that most non-technical people don't want to deal with. They want a WYSIWYG editor, and will cry, kick, scream, and intentionally be completely unproductive until they get it.