OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

docbook message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: Re: [docbook] Migrating from DTD to RNG Schema

Hi Giuseppe,

On Sonntag, 13. November 2011, 18:15:59 Giuseppe Greco wrote:
> I'm trying to migrate all my stuff from DTD to RNG Schema... and more or
> less it is clear to me how to proceed. Anyway, I'm wondering how to
> migrate my entity catalog:
> [...]

Do you know the "DocBook V5.0 Transition Guide"?


Especially the section "What About Entities?" is probably interesting and may 
be worth a read to get an overview about entities in DocBook 5.

Apart from the information mentioned before, I see the following options to 
handle entities in DocBook 5:

1. You can incorporate your entity declarations by pointing it to a file 
   (inside the DOCTYPE header):
   <!DOCTYPE book [
     <!ENTITY % entities PUBLIC
      "-//AGAMURA//ENTITIES Localization V1.0//en-US"
   If your book contains several chapters and are included by xi:include
   elements, you'll need to integrate the above header in each file. Of
   course, you need correct catalog entries, otherwise it won't work.
   Furthermore, the above DOCTYPE declaration does NOT refer to a DTD; this
   is on purpose. As you validate with the aid of DocBook's RELAX NG schema
   this is not necessary anymore nor helpful.

   Another idea is to "simplify" the URI and l10n.ent file and reduce the
   complexity and "nesting level". 
   The above example is useful for an English book. For a German book, you
   could replace "...//en-US" with "...//de-DE". Probably you need to
   point not to a "l10n.ent" file but to a file which contains all the
   German declarations.

2. You can replace any entity with <ref/> (transclusion)
   This is a pretty new method developed by Jirka Kosek and is known as
   a "transclusion" method for DocBook. The (rough) idea is to collect 
   all your placeholder content in an <info> element and use <ref/> to
   refer to them. You can read more here:


   Of course, you need to resolve the <ref/> elements to get the real 
   content. This is done by a XSLT processing step.
   As far as I know, it might be not a recommendation yet, blessed by the
   OASIS committee. Therefore there is a customization for the DocBook 

Hope this helps. :)

  Thomas Schraitle

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]