From 261d6237a0cbfc8281cffa149f2088e1797ce211 Mon Sep 17 00:00:00 2001
From: Bob Stayton <bobs@sagehill.net>
Date: Sat, 17 Mar 2012 21:22:10 +0000
Subject: [PATCH] More explanation of relative paths in glossary.collection.

---
 xsl/params/glossary.collection.xml | 17 +++++++++++++++--
 1 file changed, 15 insertions(+), 2 deletions(-)

diff --git a/xsl/params/glossary.collection.xml b/xsl/params/glossary.collection.xml
index 99dab5419..5d5f80301 100644
--- a/xsl/params/glossary.collection.xml
+++ b/xsl/params/glossary.collection.xml
@@ -187,8 +187,21 @@ occur in precisely the order they occur in your database.</para>
 customization layer or directly through your processor's interface) to
 point to your global glossary.</para>
 
-<para>A relative path in the parameter is interpreted as relative
-to the file containing the empty glossary element in your document.</para>
+<para>A relative path in the parameter is interpreted in one
+of two ways:</para>
+<orderedlist numeration="loweralpha">
+  <listitem>
+    <para>If the parameter <literal>glossterm.auto.link</literal>
+    is set to zero, then the path is relative to the file containing
+    the empty <tag>glossary</tag> element in the document.</para>
+  </listitem>
+  <listitem>
+    <para>If the parameter <literal>glossterm.auto.link</literal>
+    is set to non-zero, then the path is relative to the file containing
+    the first inline <tag>glossterm</tag> or
+    <tag>firstterm</tag> in the document to be linked.</para>
+  </listitem>
+</orderedlist>
 
 <para>The stylesheets will format the glossary in your document as if
 all of the entries implicilty referenced appeared there literally.</para>
-- 
2.50.1