ph with keyref is not converted to link in PDF output [DOT 2.x develop branch]
See original GitHub issueIf my DITA Map has a key definition like:
<topicref keys="CONTAINER" href="topics/care.dita">
<topicmeta>
<linktext>CONTAINER</linktext>
<keywords>
<keyword>CONTAINER</keyword>
</keywords>
</topicmeta>
</topicref>
and another DITA topic has a keyref like:
<ph keyref="CONTAINER"/>
in the XHTML output the keyref becomes a link. But in the PDF output it does not.
Issue Analytics
- State:
- Created 8 years ago
- Comments:14 (10 by maintainers)
Top Results From Across the Web
Why are Hyperlinks not Working in PDF? Fix it!
With no Internet connection, the link present in the PDF document would not show any results. • Reason 4: Incorrect Conversion. When converting...
Read more >Adobe PDF conversion settings, Acrobat
Follow these steps to choose an Adobe PDF preset for converting files or to customize Adobe Acrobat PDF settings and compatibility levels.
Read more >Creating, saving or converting files to PDF/A
Creating, saving or converting files to PDF/A. There are many ways to save files as PDF/A or convert existing documents to PDF/A. There...
Read more >How to convert a PDF file into a Word document - Digital Trends
1. Open the PDF you'd like to convert in Acrobat. Depending on your preferences, PDF files may automatically open in Acrobat. Alternatively, if...
Read more >How to save your locked or signed pdf file into an unlocked ...
and to create a new unlocked static pdf file for merging, appending, ... This form will be converted to an XPS file. ......
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
@robander One of those cases in which the publishing engine works in slightly different way than specs and somehow users start using certain constructs based on what works in the current output. In this case maybe reusing the linktext between two key definitions might have also worked:
but not sure if it works because of https://github.com/dita-ot/dita-ot/issues/2420
Great, thanks.