Date: 10/16/01
- Next message: Jirka Kosek: "Re: [PHP-DOC] Examples"
- Previous message: j-f <email protected>: "[PHP-DOC] Bug #13696: gpc_order is deprecated"
- In reply to: Hojtsy Gabor: "Re: [PHP-DOC] Examples"
- Next in thread: Jirka Kosek: "Re: [PHP-DOC] Examples"
- Reply: Jirka Kosek: "Re: [PHP-DOC] Examples"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
From: "Hojtsy Gabor" <goba <email protected>>
> > Adding new element to DocBook doesn't break compatibility with.
> > Customizing DocBook is quite easy
> >
> > - create DocBook DTD customization (add/remove
elements/attributes)
> > - create stylesheet customizations which handle new
elements/attributes
> >
> > You can still use common tools and stylesheets. In that case
namespaces
> > are not good solutions, because you do not need combine two
DTDs, you
> > just need add one new element for seealso into existing DTD.
There is
> > nothing wrong with customizing DTD (ask Norm if you don't
beleive me;).
>
> I have seen the customization chapter of the DocBook book online,
> but the paragraphss about "A tag added? It is not docbook
anymore",
> ment to me, it is not docbook anymore...
Correct, you got my point. You can add as many tags (or elements)
you want, but than the manual couldnīt be build with the XML source
with the original DocBook.
Most elements have a default rendering scheme. We can only
standardize the names of attribute names and hope someone have time
making the customizing, so that the rendering looks better then the
default.
-Egon
- Next message: Jirka Kosek: "Re: [PHP-DOC] Examples"
- Previous message: j-f <email protected>: "[PHP-DOC] Bug #13696: gpc_order is deprecated"
- In reply to: Hojtsy Gabor: "Re: [PHP-DOC] Examples"
- Next in thread: Jirka Kosek: "Re: [PHP-DOC] Examples"
- Reply: Jirka Kosek: "Re: [PHP-DOC] Examples"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

