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] | [Elist Home]

Subject: RE: DOCBOOK: Re: Modular Documentation

> -----Original Message-----
> From: Matt G. [mailto:matt_g_@hotmail.com]
> Sent: Tuesday, February 12, 2002 7:52 AM
> To: docbook@lists.oasis-open.org
> Subject: DOCBOOK: Re: Modular Documentation
> So, if I have a set of terms relating to a standard, perhaps 
> an ITU spec or 
> an RFC, I create entities for all of these, and place them in 
>  their own 
> file.  Every document that uses these terms includes this 
> file (in the 
> document's internal subset, it declares an external parameter 
> entity that 
> maps to the file with the definitions, and then it expands 
> that entity, so 
> the definitions are instantiated in the document).  

Two short notices: 

1) You can import the entity files for global entities in your customization
this prevents the import into every single file.

2) It's *very* useful to build a hierarchy of entity files for this, like

customization layer imports globals.ent
globals.ent imports abbreviations.ent; textmodules.ent etc.
textmodules.ent e.g. imports all entity files from a directory named
textmodules (so it can be generated automatically)
and so on.

Another approach would be to build such files (like textmodules.ent) out of
a database, e.g. for product names, perhaps using an existing database ...

Gisbert Amm

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

Powered by eList eXpress LLC