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.

LwDita key references not working

See original GitHub issue

Expected Behavior

I am trying to use Markdown DITA (LwDita) to reference other topics by their id, as documented in

https://www.dita-ot.org/dev/topics/markdown-dita-syntax-reference.html#markdown-dita-syntax-reference__key-references

They are however rendered empty in PDF. My ditamap:

<?xml version="1.0"?>
<!DOCTYPE map PUBLIC "-//OASIS//DTD DITA Map//EN" "map.dtd">
<map>
  <topicref href="dbus.envcon.version.md" keys="dbus.envcon.version" format="mdita">
    <topicref href="dbus.envcon.version.hardwareVersion.md" keys="dbus.envcon.version.hardwareVersion" format="mdita"/>
  </topicref>
</map>

My dbus.envcon.version.md file:

---
id: dbus.envcon.version
---
# DBUS Interface `envcon.version`
Version information from Envon     Hardware

See  [dbus.envcon.version.hardwareVersion] ...

See  [dbus.envcon.version.hardwareVersion](dbus.envcon.version.hardwareVersion.md) ...

My dbus.envcon.version.hardwareVersion.md file:

---
id: dbus.envcon.version.hardwareVersion
---
# DBUS Property `envcon.version.hardwareVersion`
Hardware version information from Envon HW

Actual Behavior

Only the second “See” link is rendered (pdf output), the first one is empty:

Version information from Envon Hardware
See ...
See DBUS Property envcon.version.hardwareVersion on page 3 ...

Steps to Reproduce

render the given ditamap / md files with dita-ot 3.3.4 or dita-ot 3.5.4.

Environment

Java: Oracle Java 11.0.9+7-LTS
Dita-ot 3.3.4 and 3.5.4 tested.
Operating system and version: Ubuntu Linux 20.04
How did you run DITA-OT? dita --input dbus.envcon.version.ditamap -f pdf
Transformation type: pdf

Issue Analytics

State:
Created 3 years ago
Comments:10 (2 by maintainers)

Top GitHub Comments

1reaction

raducoravucommented, Jul 19, 2021

If in the build file “dita-ot/plugins/org.dita.pdf2/build.xml” I replace the dependency to the “preprocess2” task:

 <target name="dita2pdf2" depends="dita2pdf2.init, build-init, preprocess2, map2pdf2, topic2pdf2"/>

with the one to the old “preprocess” task:

 <target name="dita2pdf2" depends="dita2pdf2.init, build-init, preprocess, map2pdf2, topic2pdf2"/>

this seems to work for me.

0reactions

hcw70commented, Aug 9, 2021

So who can investigate and provide a fix here? Who knows about preprocess / preprocess2 and can provide a merge request?

Top Results From Across the Web

Resolve key references (keyref) - DITA Open Toolkit

Resolve key references (keyref). The keyref step examines all the keys that are defined in the DITA source and resolves the key references....

Specification URIs - OASIS Open

For variable text, such as product names, authors can use key references on phrase (XDITA) or span (HDITA). For a complete list of...

How to import and export LwDITA in PageSeeder – Tutorials

We're still working on this article, so it might contain ... model the LwDITA format in PSML;; import LwDITA as PSML using map...

Getting Started with LwDITA in Adobe FrameMaker

Add these lines into the C:\Program Files\Adobe\Adobe FrameMaker 2022\fminit\ditafm\ditafm.ini file. They are broken out here to make it very easy to select ...

Lightweight DITA - DITA-OT mdBook Demo

Attention: Since Lightweight DITA has not yet been released as a formal ... XDITA is the LwDITA authoring format that uses XML to...