DITA and XMetaL Discussion
XMetaL Community Forum › DITA and XMetaL Discussion › Purposely Excluded Conrefs Still Listed in Output Log as missing
-
Penthesilea June 24, 2009 at 2:30 pm
Purposely Excluded Conrefs Still Listed in Output Log as missing
June 24, 2009 at 2:30 pmParticipants 1Replies 2Last Activity 13 years, 9 months agoBelow is an example of the errors listed in the output log. The conref below has been exclude using a conditional product tag; however, it is still listed as missing.
We have just begun implementation; however, I'm concerned these errors will pollute the output log to the point where it is unusable or potentially cause other problems. Is there something in our implementation causing this or should we simply ignore. XMetaL version 5.01
*****************************************************[xslt] [DOTX010E][ERROR]: Unable to find target for conref=”../Conrefs/ct_2D_platform.xml#ditacomponent_9C444A9F1B664CABAC90EE0D6693AF52/section_B447582BEFB643228D159AF8D521672A”.
Check to make sure that the target element is available, and that it is a 'xxxx'
element. Note:'../Conrefs/ct_2D_platform.xml#ditacomponent_9C444A9F1B664CABAC90EE0D6693AF52/section_B447582BEFB643228D159AF8D521672A'
might be changed to use default dita topic file extension name '.dita' or '.xml'. Check
to make sure the target of conref is correct.severin.foreman June 24, 2009 at 2:55 pm
Reply to: Purposely Excluded Conrefs Still Listed in Output Log as missing
June 24, 2009 at 2:55 pmWe had this issue. It occurs when the conditional processing attribute value is set on the conref target instead of on the element that contains the conref attribute. The reason is that, during processing, the open toolkit filters content based on your conditional text settings before it resolves conrefs. To resolve the issue, set the product attribute value on the same element that has the conref.
=== The wrong way to do it ===
Topic A contains a paragraph that conrefs from Topic B.
Topic A
The paragraph in Topic B has the product attirbute set and
a DITAVAL file excludes the content from the build.
Topic B
Some text.
When the OT processes these files, the paragraph in topic B is removed before the conref is resolved. Thus, the conref is broken. The output will probably appear the way you want, but it makes your error logs much less useful, as you noted.
=== The right way to do it ===
Topic A contains a paragraph that conrefs from Topic B, but this time the paragraph in topic A is
removed from the topic before conrefs are resolved.
Topic A
Topic B
Some text.
Reply to: Purposely Excluded Conrefs Still Listed in Output Log as missing
June 24, 2009 at 3:00 pm -
AuthorPosts
- You must be logged in to reply to this topic.
