[ docbook-Bugs-925117 ] Whitespace not normalized for XEP index keys

[SourceForge.net <no...@so...>]

Bugs item #925117, was opened at 2004-03-28 20:14
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=373747&aid=925117&group_id=21935

Category: DocBook XSL FO
Group: DocBook V4
Status: Open
Resolution: None
Priority: 5
Submitted By: Kevin Yank (kyank)
Assigned to: Nobody/Anonymous (nobody)
Summary: Whitespace not normalized for XEP index keys

Initial Comment:
In DocBook XML documents where whitespace within
<indexterm> tags is not normalized, RenderX XEP can
report index errors and page references can go missing
on index terms when $xep.extensions = 1.

In /docbook/xsl/fo/index.xsl, the following templates
output index keys for RenderX XEP:

<xsl:template match="indexterm" name="indexterm">
<xsl:template match="indexterm[@class=&#039;startofrange&#039;]">

The code that performs this output uses simple value-of
tags to output the values of primary, secondary, and
tertiary tags, which do not normalize whitespace:

<xsl:value-of select="primary"/>

Spaces are also not normalized when generating the
rx:index-item tags in the following templates in
docbook/xsl/fo/autoidx.xsl:

<xsl:template match="indexterm" mode="index-primary">
<xsl:template match="indexterm" mode="index-secondary">
<xsl:template match="indexterm" mode="index-tertiary">

The values of the rx:index-item tags generated by
autoidx.xsl must exactly match the values of the rx:key
attributes generated by index.xsl for the page
references to be correctly generated at render time.
Because spaces are not normalized, errors and missing
page references sometimes occur when multiple
occurrences of a single indexterm differ in their
whitespace.

To correct these problems, normalize-whitespace() must
be used in outputting the values. Patched copies of the
latest index.xsl and autoidx.xsl files from CVS that
correct this bug are attached.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=373747&aid=925117&group_id=21935