Missing files when exporting a ditamap

[ratrace]

Hi,

I have been trying to use the Export DITA map feature to export content for translation. However, I have a problem with missing files. It seems like keyrefed topics do not get included in the export.

I have used keyrefs to override some of the hrefs in the ditamap, and the keys are defined in a separate ditamap, something like this:

(NB: not the actual code)

Code: Select all

<ditamap>

 <mapref href="keydefs/keydef.ditamap" />

 <topicref href="concepts/oldtopic.dita" keyref="newtopic" />

</ditamap>

In this case the topic referenced in the keydef.ditamap does not get exported.

Maybe this has something to do with how the keys are resolved? Any clues on how this can be solved, or is it a bug?

Thanks!

/Sam

[iulian_velea]

Hello Sam,

I tested your case and it is possible that may be a problem in the gather references from a DITA Map mechanism. From what I tried, I think that the export DITA Map operation produces the correct result, but the DITA Map Manager doesn't resolve correctly the topic referenced using the keydef from the referred map. I added an issue on our tracker and you will be notified of the result.

Thank you,
Iulian

--
Iulian Velea
<oXygen/> XML Editor, Schema Editor and XSLT Editor/Debugger
http://www.oxygenxml.com

[ratrace]

Thank you Iulian,

Strange, on my end it's the other way around. The DITA Map Manager seems to behave correctly, but the DITA map export misbehaves.

/Sam

[iulian_velea]

Hello Sam,

In this case I think it would be better if you could send us a set of sample files on our technical support email address, [support@oxygenxml.com]. This way we can reproduce exactly your problem and take further action.

Regards,
Iulian

[ratrace]

Thanks,

I'll do that; however, I've looked a bit more deeply into the issue, and my first description of the problem was not entirely correct. What actually happens is that the keyrefed file does get included in the export, but the original href that is overridden by the keyref does not. This might very well be the expected behavior. However, if the key is undefined I would expect that there would be a fall back to the href value? That is how the DITA Map Manager behaves, and also the DITA OT.

I currently rely on this behavior to sometimes replace certain topics with alternate versions, so I need the original href to be included if the key is undefined. But maybe I've been a little too creative...

/Sam

[iulian_velea]

Hello,

Thank you for the sample files and explaining exactly was is the case when the problem occurs. Following your description I reproduced the behavior and updated the issue related to it.
We will notify you when a conclusion is reached.

Best regards,
Iulian