You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[java] [PDFX005F][FATAL]: Topic reference (href : #unique_28) not found. Reference may be incorrect. Please correct your ditamap or bookmap file.The location of this problem was at (File = D:\projects\eXml\samples\dita\it-book\m_eur_glossary.ditamap, Element = topicref:1)
Looking in the "topicmergeImpl.xsl" it seems to me that all attributes of are ignored:
I attached a sample DITA project, in DITA OT 1.5.4 the error when publishing to PDF is:
[java] [PDFX005F][FATAL]: Topic reference (href : #unique_1) not found. Reference may be incorrect. Please correct your ditamap or bookmap file.The location of this problem was at (File = C:\Users\radu_coravu\Desktop\testGlossentry\glossmap.ditamap, Element = topicref:1)
I'm using DITA OT 1.6.1 and the problem still remains, one of our clients reported it again.
The workaround is to make the reference in the DITA Map something like:
Converted from SourceForge issue 3504470, submitted by @raducoravu
The DITA 1.2 specification for
<glossarylist>
states that it could have an @href attribute (and that so could<toc>
).So why doesn't a construct like this in a bookmap work?
Such a construct produces a fail like:
Looking in the "topicmergeImpl.xsl" it seems to me that all attributes of are ignored:
The match for
<toc>
is more interesting, it actually matches any<toc>
without an@href
:Maybe the same thing could be done for
<glossarylist>
. Maybe.The text was updated successfully, but these errors were encountered: