Re: [docbook-apps] glossterm collection > There's no entry for [glossterm-value]

["Bob Stayton" <bobs at sagehill dot net>]

Although forming a link based on text matching is always going to be risky,
I would consider this particular problem to be a bug.  It can be easily
fixed by applying the XSL normal-space() function on both ends of the
comparison.  Can you file a bug report?

As a workaround, you could add a baseform="Asynchronous Digital Subscriber
Line" attribute to the inline glossterm.  That will be used to form the
match instead of the glossterm's text content.  But then you need to see if
your pretty printer adds line breaks to attribute values as well.  It seems
like it shouldn't.

Bob Stayton
Sagehill Enterprises
DocBook Consulting
bobs@sagehill.net


----- Original Message ----- 
From: "Sean Wheller" <sean@enbaya.co.za>
To: <docbook-apps@lists.oasis-open.org>
Sent: Friday, October 08, 2004 1:28 PM
Subject: [docbook-apps] glossterm collection > There's no entry for
[glossterm-value]


> Hi,
>
> When doing dynamic glossentry collection I get
> "There's no entry for [glossterm-value] in /path/to/glossary.xml"
> from Saxon.
>
> This only occurs for glossterms whose value is on two lines, like this:
> "broadband technology such as <glossterm>Asynchronous {line break here}
>  Digital Subscriber Line</glossterm> (<acronym>ADSL</acronym>), provide a
..."
>
> When the element pair is on the same line the glossentry is found in the
> database and output to the document.
>
> Now I can do XPath on glossterm and manually fix each such instance,
making
> sure the element pairs are on a single line, but next time I use "Pretty
> Print" to neatly indent the markup I am sure to lose this work.
>
> I searched the archive, but that thing is so big, it's like looking for a
> needle in a haystack. There is also no bug submitted. Have others had this
> problem or is this a new bug?
>
> OASIS  DocBook  XML  DTD 4.2
> DocBook  XSL 1.66.1
> SAXON_6 6.5.3
> -- 
> Sean Wheller
>
>