Links in DITA Word output format

[andreas_tai]

We are using the excellent DITA integration in Oxygen. But we have problem to generate links with the (still) experimental "DITA Map MS Office Word" Transformation scenario.

We enclose the links in a related-links element

Code: Select all

 <related-links>

      <link href="https://foo.com" format="pdf">

         <linktext>https://foo.com/doc.pdf#page=52</linktext>

      </link>

   </related-links>

In the word document the links do not appear and instead of "Related Links" each topic contains a header "Related Topics" with no content underneath.

If we list the links in the body, e.g.

Code: Select all

         <ul>

            <li><xref href="http://foo.com" format="html">http://foo.com</xref></li>

            <li><xref href="https://foo.com/doc.pdf" format="pdf">http://foo.com</xref></li>            

         </ul>

...the link text appears but the links are not active (they are not formatted as Links with a specific URL).

We also tried to set args.rellinks parameter to "all" but this does not make any difference.

Is there a way to get the links in the Word Output?

Thanks so much and best regards,

Andreas

[Radu]

Hi Andreas,

My hint for you would be to set the @scope="external" attribute on those external links.
If this still does not work, the DITA Open Toolkit bundled with Oxygen indeed offers DITA to Word output using Jarno Elovirta's DITA OT plugin:

https://github.com/jelovirt/com.elovirta.ooxml

so maybe you can prepare a small sample DITA project, zip it and add an issue on the project.

Regards,
Radu

[andreas_tai]

Hi Radu,

Thanks so much for your fast reply!

Setting the scope attribute of the xref element to "external" indeed did the job: now not only the link text is shown, but the links are also active!

Every external link under related-links is still not shown but we can absolutely live with the solution and move the links to the body element.

Thanks again for your perfect support : )

Best regards,

Andreas

[Radu]

Hi Andreas,

Good that you have a workaround now. I also added an issue for the related links problem:

https://github.com/jelovirt/com.elovirt ... /issues/15

Regards,
Radu

[andreas_tai]

Thanks a lot, Radu!!