DocBook is a collection of XML standards and tools for technical publishing. The DocBook document type definition (DTD) was developed during the 1990s to provide an application-independent method for creating computer documentation. But the basic 'book' features of DocBook can be used for other kinds of content, so it has been adapted to many purposes. DocBook is often compared against DITA, a similar but newer XML schema.
DocBook and DITA both have their places. They're both excellent for single sourcing. DocBook is better for what I call monolithic single sourcing, while DITA is better suited for discrete single sourcing.
If you follow the latest trends or have been to a conference recently, you may find the idea of choosing an XML schema puzzling. Isn't the question really, 'How should I customize DITA to do what I want'? While there are many good reasons to choose DITA, it's not the only schema in town.
Both the DITA and the DocBook specification are quite alive and well in organizations, and each is evolving into its own distinct application niches, with DITA looking to be turning into the default standard for large scale enterprises, while DocBook works more effectively at the small to intermediate level. What’s perhaps more interesting is the Microsoft Word, even with support for XML as provided by OOXML, is not making as much of an inroad in the structured document market, in great part because it is fairly difficult to constrain people’s use of the word-processing program to a limited, finite subset of potential styles.
The DocBook document type definition (DTD) was developed during the 1990s to provide an application independent method for creating computer documentation. Versions of the DocBook DTD have been created for both SGML and XML. You can create an embedded index in DocBook using index elements.
There are a number of tools available for transforming DocBook XML documents to various formats. All of these tools have strengths, as well as some noticeable weaknesses and drawbacks. This article looks at the benefits of using the XMLmind FO Converter, a graphical, highly configurable, and cross-platform application designed to transform DocBook XML files to any supported output format.
This howto attempts to clear the fog and mystery surrounding the DocBook markup system and the tools that go with it. It is aimed at authors of technical documentation for open-source projects hosted on Linux, but should be useful for people composing other kinds on other Unixes as well.
Having new DocBook standards in place may do little to push adoption. An important factor in driving user adoption is the availability of software that implements the standard. It would be interesting to see whether big software companies would jump on the bandwagon...Unless the open-source community comes to the rescue!
XML is the future. You hear it at every conference you go to, in every magazine you pick up, in every article you read on-line. For technical writers, right now that future comes down to two products—DocBook or DITA. But what exactly are they, and which one should you choose? They are schemas for creating XML.
With DITA implementations on the rise, and an entrenched DocBook community already in place, the resulting market interest has spurred interest in automated DocBook to DITA conversion. So I would expect offerings of automated DocBook to DITA conversion scripts to emerge in the next 6-10 months. This article addresses the real questions, "What should I expect from automated tools?" and "Will they work for me?" from the viewpoint of live experience with numerous DocBook to DITA conversions. The answers to these questions are not usually obvious.
More than a decade ago DocBook became the standard for the few brave souls forging ahead in XML publications. DocBook offered a cheaper and more efficient way to publish to multiple formats. Single-sourcing became a reality for hardware and software companies. However, in recent years, many in technical documentation publications have proclaimed DITA as the standard for XML documentation. DITA offered architecture in which to create and publish structured content. Are these two seemingly rival standards really that different? This article from Teresa Mulvihill answers this question with comparative examples, and allows you, the audience, to decide for yourselves.
DocBook is a collection of standards and tools for technical publishing. DocBook was originally created by a consortium of software companies as a standard for computer documentation. But the basic 'book' features of DocBook can be used for other kinds of content, so it has been adapted to many purposes.
Gets you started with DocBook, an SGML/XML dialect that describes the content of technical articles and other documents. David discusses the benefits of using DocBook, and then describes how to plan and modularize a large document conversion project.
First of all, understand that you don’t have to learn it. Every year more and more toolds come out that help place a layer between you and the native XML. In a few years time you will hardly even realise there is XML underneath.