dita-ot: Can no longer use conref in keydef metadata [DOT 2.3]

If in my DITA Map I define a key which has a keyword with a conref to another one defined in a topic:

     <keydef keys="company_name_full">
      <topicmeta>
        <keywords>
          <keyword
            conref="abc.dita#abc/company_full"/>  
        </keywords>
      </topicmeta>
    </keydef>

and in some topic I use the key:

<ph keyref="company_name_full"/>

it no longer gets expanded. Using DITA OT 1.8 the key got expanded.

About this issue

Original URL
State: closed
Created 8 years ago
Comments: 22 (19 by maintainers)

Commits related to this issue

Fix conref in keydef value in preprocess2 Fixed the case when a map uses a topic as a conref target but the topic is not referenced with a topicref. Partial fix for #2420. Signed-off-by: Jarno Elovi... — committed to dita-ot/dita-ot by jelovirt a year ago
Fix conref in keydef value in preprocess2 Fixed the case when a map uses a topic as a conref target but the topic is not referenced with a topicref. Partial fix for #2420. Signed-off-by: Jarno Elovi... — committed to dita-ot/dita-ot by jelovirt a year ago

Most upvoted comments

#4258 is a partial fix to this issue. You no longer need to reference conref targets separately with a <topicref>. It doesn’t fix this issue completely. A workaround is Instead of

<keydef keys="company_name_full">
  <topicmeta>
    <keywords>
      <keyword conref="abc.dita#abc/company_full"/>  
    </keywords>
  </topicmeta>
</keydef>

you need to use

<keydef keys="company_name_full">
  <topicmeta>
    <keywords>
      <keyword><text conref="abc.dita#abc/company_full"/></keyword>  
    </keywords>
  </topicmeta>
</keydef>

jelovirt on Aug 5, 2023