question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Using "appendices" wrapper causes PDF2 failure or error

See original GitHub issue

Using the latest development code, I am trying to reuse a set of appendices from one bookmap inside of another, so I wrapped them in the <appendices> element:

<appendices id="app">
<appendix href="bookapp1.dita"/>
<appendix href="bookapp2.dita"/>
</appendices>

When @href is specified on the <appendices> element, the PDF looks fine. When there is no @href as in the sample above, output is broken. AH returns a PDF without the two topics (though the titles appear in the contents / bookmarks). It also generates the following errors:

      [ahf] Error Code  : 10769 (2A11)
      [ahf] Unresolved id value: "_OPENTOPIC_TOC_PROCESSING_d68e2780".
      [ahf] Line 1, Col 20232, file:///C:/Users/IBM_AD~1/AppData/Local/Temp/temp20151008163148010/topic.fo
      [ahf] Error Level : 2
      [ahf] Error Code  : 10769 (2A11)
      [ahf] Unresolved id value: "_OPENTOPIC_TOC_PROCESSING_d68e2867".
      [ahf] Line 1, Col 20849, file:///C:/Users/IBM_AD~1/AppData/Local/Temp/temp20151008163148010/topic.fo

When I try with FOP, I get Java errors and no PDF.

Issue Analytics

  • State:closed
  • Created 8 years ago
  • Comments:13 (12 by maintainers)

github_iconTop GitHub Comments

1reaction
adambherecommented, Apr 25, 2016

Tried with Apache FOP and no attributes on the element. Got no errors, but the PDF output does not include the individual appendices (appendix elements and their content). In DITA OT 1.8.5, it was possible to wrap any number of <appendix> elements in <appendices>, with appendices including neither @navtitle nor @href, and the individual <appendix> elements were rendered in PDF.

A work-around seems to be to add @navtitle or @href to the <appendices> element. This causes the nested <appendix> elements to be rendered, but results in an unwanted “Appendix” page, similar to a part front page.

The ideal solution would be to render <appendices> only if a @navtitle or @href is provided, otherwise, render only the nested <appendix> elements. In other words the following:

<appendix href="appendix_topic1.dita" />
<appendix href="appendix_topic2.dita" />

… and this:

<appendices>
    <appendix href="appedix_topic1.dita" />
    <appendix href="appendix_topic2.dita" />
</appendices>

… should both result in only appendix_topic{x}.dita being rendered.

I’d be happy to override the existing behaviour in our PDF plug-in, but have not yet identified the code area to modify: any tips would be appreciated.

0reactions
robandercommented, May 17, 2017

@infotexture yes - that is correct. That’s … not really the same as the original issue, which was that if I have plain <appendices> with no title or @href I previously got errors + every nested appendix topic was missing.

It’s probably worth having another issue for this (I’d like to be able to fix it too but don’t have a pull request in the queue for it, so an issue will keep it from getting lost).

Read more comments on GitHub >

github_iconTop Results From Across the Web

Adding section to appendix causes a compile error
What does this harmless subsection command? It starts a new page! And this page has a different page style. The first page has...
Read more >
z/OS XL C/C++ User's Guide
This section describes how to read syntax diagrams. It defines syntax diagram symbols, items that may be contained within the diagrams ...
Read more >
Changes_XErase.txt
This can cause the Purge erasure to fail falsely, while the fallback Clear operation is fine. GetNewStats has been upgraded to provide either...
Read more >
Aspera Orchestrator User Guide - 400 Bad Request - IBM Aspera
If the new active directory fails, an error message appears, citing the specific reasons for failure and giving instructions for retrying the process....
Read more >
DITA OT release 1.4.1 - Titania Delivery
2.2.5: Error messages and troubleshooting ... 3.3.1.3.14.1: XHTML migration for flagging updates in DITA-OT 1.7 ... Appendix A: DITA-OT release history.
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found