Any link to a dlentry element is broken in PDF
See original GitHub issueWith either DITA OT 1.8 and 2.x:
I have a topic with a definition list containing a dlentry:
<!DOCTYPE topic PUBLIC "-//OASIS//DTD DITA Topic//EN" "topic.dtd">
<topic id="gogu">
<title>GOGU</title>
<body>
<p><dl>
<dlentry id="dlentry_spq_wtg_r5">
<dt>aaaa</dt>
<dd>bbbbbb</dd>
</dlentry>
</dl></p>
</body>
</topic>
and a topic which has a link to it:
<!DOCTYPE topic PUBLIC "-//OASIS//DTD DITA Topic//EN" "topic.dtd">
<topic id="gigi">
<title>GIGI</title>
<body>
<p><xref href="gogu.dita#gogu/dlentry_spq_wtg_r5">THIS IS A TEST</xref></p>
</body>
</topic>
In the PDF output, the link is broken, when Apache FOP processes, it issues warnings like:
[fop] 7764 WARN [ main ] org.apache.fop.apps.FOUserAgent - Page 3: Unresolved ID reference "unique_2_Connect_42_dlentry_spq_wtg_r5" found.
Issue Analytics
- State:
- Created 8 years ago
- Comments:17 (16 by maintainers)
Top Results From Across the Web
dlentry - Oxygen XML Editor
The dlentry element groups a single entry in a definition list (dl). The dlentry element includes a term (dt) and one or more...
Read more >DITA Open Toolkit 2.2.5 Release Notes
#1709, #2327; Links to <dlentry> elements were broken in PDFs generated via Apache FOP, as FOP does not support the @id attribute on...
Read more >DITA-OT error messages - GitHub Pages
This message may indicate a reference to an invalid file (such as accidentally referencing a PDF or unknown XML file as if it...
Read more >PDF Download in HREF of a-element results in empty PDF
The result is an broken PDF. Results in broken PDFs. I am not sure if that makes any sense. My PDF-data starts like...
Read more >Error messages - Titania Delivery
Message ID Severity Message text
DOTJ051E Error Unable to load target for coderef "%1".
DOTJ054E Error Unable to parse invalid %1 attribute value "%2"
DOTJ055E Error...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Closed with #1764 as described above.
Commit linked to above overrides default processing for
dlentry/@id
with FOP to drop it from the table row, and create the markup Eliot suggested (<fo:inline id="ID"/>
in the first term). No change to processing for AH or XEP.The more general post-process that @jelovirt mentioned would still be useful for links to any other
fo:table-row
, but I went with the easy fix for the common scenario. If/when a general post-process is added to fix this, the specific fix for<dlentry>
will be unnecessary, but will not interfere in any way.