[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [docbook-apps] DocBook Customization
Hi Eric,
My impression is that many groups adopt DITA
because they want to work in topics rather than chapters. Then they do whatever
is needed to use DITA to write topics. I have been in
contact with more than one group that has adopted DITA without any DTD
customization. As you say, people often do crazy things.
8^)
One common DocBook customization practice is to cut
down on the number of elements. There are several reasons why:
a. When using an XML editor that presents a
list of valid tag names, the list can be quite long in many contexts (such as
inlines). Many such elements are never to be used, so remove them from
sight.
b. Reducing ambiguity in choosing among
similar elements.
c. Reducing the complexity of a stylesheet
customization. If you know you are only supporting certain elements you don't
need to have templates for all elements.
d. Reduce the complexity of the para element
by removing block element children (making it like simpara).
It is possible to make a subset that still produces
documents that validate with the full DocBook schema. But of course not the
other way around.
In terms of the cost of customization, I have found
customizing the DocBook 4 DTD to be easier than customizing the DITA DTDs. In
DITA's DTDs, everything is a twice-removed parameter entity, and it is hard to
keep track of where an element is actually declared and what children it can
contain. DocBook 4 uses parameter entities, but not to such a complex
degree. DocBook 5's RelaxNG grammar is even easier to customize, once you
learn the grammar.
|
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]