glossentry reports missing if used in shortdesc and another topic uses <xref> to origin topic #3153
Labels
bug
preprocess
priority/medium
Medium (or unknown) priority issue
stale
No recent activity. May be closed soon.
Expected Behavior
When
<term keyref="gloss_term"/>
is used in a<shortdesc>
the value needs to resolve when shortdesc is read.Actual Behavior
The glossterm is left blank:
Possible Solution
I am not sure if this is a keyref issue or a topicpull issue. I would think that the keyref would already be resolved by the time topicpull happens. The keyref is trying to resolve relative to the dita-ot/xsl location rather than the doc source location.
Steps to Reproduce
My sample source and output is included in this zip: samples.zip
hierarchy.ditamap, added glossary.ditamap:
<mapref href="glossary.ditamap"/>
glossary.ditamap (new)
<topichead> <topicmeta> <navtitle>Glossary</navtitle> </topicmeta> <glossref href="glossary/gloss_google.dita" keys="gloss_google"/> </topichead>
glossary/gloss_google.dita (new):
<glossentry id="gloss_google"> <glossterm>Google</glossterm> <glossdef>The place where you find stuff.</glossdef> </glossentry>
concepts/lawnmower.xml, added term glossentry reference in
<shortdesc>
<shortdesc>The lawnmower is a machine used to cut grass in the yard. You can look it up on <term keyref="gloss_google"/></shortdesc>
concepts/oil.xml added
<link>
to lawnmower.xml:<link href="lawnmower.xml" format="dita" type="concept"></link>
dita -v --input=samples/hierarchy.ditamap --format=xhtml
In Oil.xml the term is blank:
Copy of the error message, log file or stack trace
[topicpull] java.io.FileNotFoundException: C:*****\dita-ot.git\src\main\xsl\glossary\gloss_google.dita (The system cannot find the path specified)
[topicpull] file:/C:/*****/dita-ot-docs/samples/concepts/lawnmower.xml:11:121: [DOTX031E][ERROR]: The file ../glossary/gloss_google.dita is not available to resolve link information.
Environment
dita -v --input=samples/hierarchy.ditamap --format=xhtml
Thank you for any help you can provide to fix this issue!
The text was updated successfully, but these errors were encountered: