From: Bob Stayton Date: Sun, 19 Jan 2014 21:50:34 +0000 (+0000) Subject: New param to control automatic links in index from see and X-Git-Tag: release/1.79.1~6^2~118 X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=10bd0ffd33cbfb88ca5dc5f07df61053b392cb03;p=docbook-dsssl New param to control automatic links in index from see and seealso to indexterm primary. --- diff --git a/xsl/params/autolink.index.see.xml b/xsl/params/autolink.index.see.xml new file mode 100755 index 000000000..65af1a329 --- /dev/null +++ b/xsl/params/autolink.index.see.xml @@ -0,0 +1,59 @@ + + +autolink.index.see +boolean + + +autolink.index.see +Link index see and seealso to index primary + + + + + + +Description + +If this param is set to a non-zero value, +(default = 1), then the +stylesheet will attempt for form a link between a +see or seealso element +and a matching indexterm primary element. + + +The stylesheet uses an exact text match after +applying the normalize-space() function. +If the see or seealso text contains a comma, +then only the text prior to the comma is used. +This assumes the author is using the convention "see primary, secondary" +to specify a subentry. Thus links always land on the primary +entry in the index, so the reader has to look down to see the +secondary entry. +If there is no match on a +primary, no link is formed, but the text +still displays. + +No attempt is made to automatically link to text in +secondary or tertiary elements. + + +If this parameter is zero, then +no automatic links from see and seealso +are formed within the index. + +?Trying to form manual links to indexterm +child elements such as primary or +secondary may produce erratic results. +Duplicate entries in an index are merged during processing, and +not all id attributes on those child elements are copied through +to the output. + + + + +