This is the mail archive of the
docbook-apps@lists.oasis-open.org
mailing list .
Re: Re: DOCBOOK: Glossary
- From: Katharina Udemadu <katharina dot udemadu at WiredMinds dot de>
- To: David Cramer <david_cramer at broadjump dot com>
- Cc: Jirka Kosek <jirka at kosek dot cz>, docbook-apps at lists dot oasis-open dot org
- Date: Fri, 04 Jan 2002 13:05:01 +0100
- Subject: Re: DOCBOOK-APPS: Re: DOCBOOK: Glossary
- Organization: WiredMinds Informationssysteme GmbH
- References: <D4FE6E460E61224DB78998FB118EC4F116F723@ARACHNE.inhouse.broadjump.com>
Thanks a lot, David. It works very well.
I am now using the glossify.xsl as preprocessing step, then I am running the
result through jade + DSSSL. This does the job (at the moment).
Katharina
David Cramer schrieb:
> Katharina,
> I haven't looked at biblio.xsl, but here's an xsl that I had our
> developers write for me to use as a preprocessing step. To use it,
> include the master glossary in your document (e.g. as an entity), then
> run this xsl on it. glossify.xsl removes any glossentries that aren't
> used in the document or in the glossdefs or glossseealsos of terms that
> are used (i.e. it's recursive). It also sorts the glossentries and
> removes any glossdivs. Note: it's not smart enough to deal with
> something like <glossterm><acronym>XML</acronym><glossterm> in the
> glossary. Take the resulting document and run it through norm's xsls to
> get your output.
>
> I'd posted an earlier version of this here a while back. The previous
> one required three separate xsls, now it's down to one. I recommend
> using Saxon for glossify.xsl. Xalan is very slow for this task.
>
> David