forrest-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andreas Hartmann" <>
Subject RE: Document DTD vs. Docbook DTD
Date Thu, 28 Feb 2002 17:50:30 GMT

*********** REPLY SEPARATOR  ***********

On 28.02.2002 at 18:34 Steven Noels wrote:

>Stefano wrote:
>> This is a holy war and I don't want to fight it.
>It is, indeed. Docbook tries to be everything to anyone, and as such is
>a very complex authoring DTD to fully support, if only for relatively
>short webpages. Plus I like having meaningful elements when authoring
>specific documents, hence project-info.xml and the like. But maybe that
>is because I am using a 'real' DTD-configured XML editor for such
>tasks - perhaps text-editor-users are more than happy with a template
>> Just one thing: there is a lot of content already written in
>> docbook in
>> the world and a lot of content written using Document DTD (various
>> versions, but almost equivalent), so we should support both
>> in order to
>> avoid loosing some content.
>> But how should we do that?
>I'm not convinced we should transform 'across Docbook' other than for
>showing off Cocoon's pipeline power. We could however support Docbook
>for specific content types such as (user/reference) manuals and more
>lenghty documents.

<precocious mode>
The more complicated the DTD is, the less people will want to write
</precocious mode>

I agree.

>Having some logical-page-after-aggregation-document-type is much more
>important, I guess, as in
>Being a standards advocate, Docbook is one of the exceptions to my rule
>that one should adopt standards as much as possible.
>Commenting in our 'own' DTD's: why is the title of a section hidden
>inside an attribute?

Yes, this is a little strange. I wondered how to create some text
decoration inside the heading when I wrote one of my tutorials.


View raw message