Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Handling of @href on a <glossarylist> #1197

Closed
jelovirt opened this issue May 3, 2012 · 3 comments
Closed

Handling of @href on a <glossarylist> #1197

jelovirt opened this issue May 3, 2012 · 3 comments
Assignees
Labels
bug plugin/pdf Issue related to PDF plug-in priority/medium Medium (or unknown) priority issue
Milestone

Comments

@jelovirt
Copy link
Member

jelovirt commented May 3, 2012

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?

    <booklists>
        <glossarylist href="m_eur_glossary.ditamap" format="ditamap">
        </glossarylist> 
    </booklists>

Such a construct produces a fail like:

[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:

<xsl:template match="*[contains(@class,' bookmap/glossarylist ')]" priority="2" mode="build-tree">
    <ot-placeholder:glossarylist id="{generate-id()}">
        <xsl:apply-templates mode="build-tree"/>
    </ot-placeholder:glossarylist>
</xsl:template>

The match for <toc> is more interesting, it actually matches any <toc> without an @href:

<xsl:template match="*[contains(@class,' bookmap/toc ')][not(@href)]" priority="2" mode="build-tree">

Maybe the same thing could be done for <glossarylist>. Maybe.

@jelovirt
Copy link
Member Author

jelovirt commented May 3, 2012

Submitted by hongzhangse

hi, can you give a case base on your description? I can't reproduce the isssue using 1.6.M02

@jelovirt
Copy link
Member Author

jelovirt commented May 3, 2012

Submitted by raducoravu

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)

@raducoravu
Copy link
Member

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:

      <glossarylist>
            <topicref  href="glossary.ditamap" format="ditamap"></topicref>
        </glossarylist> 

@ghost ghost assigned jelovirt Dec 23, 2012
jelovirt added a commit that referenced this issue Dec 23, 2012
For booklist children with a topic reference, don't create a place
holder, but rather process the topic instead.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug plugin/pdf Issue related to PDF plug-in priority/medium Medium (or unknown) priority issue
Projects
None yet
Development

No branches or pull requests

2 participants