Save Ditamap as PDF - All Bookmarks Point to Same Destination

[absasenbury]

I recently moved from FrameMaker 11 to FrameMaker 2017. One of my forms of output is PDF.

When generating a PDF from a Ditamap in FM11, PDF bookmarks work perfectly, each pointing to the correct place in the document. In FM2017, however, the bookmarks all point to the same named destination, so all of the bookmarks go to the first page.

Was there a change in FM2017 that might have caused this issue? Is there something I may have overlooked when adapting my templates and EDDs from FM11 to FM2017?

[Amitoj]

Hi, Can you please share a sample of the ditamap where this issue may be coming so we can look at the same at our end.

thanks,

[absasenbury]

Sure. Here's the XML from an example DITAMAP that I made to send to Adobe support:

<?xml version="1.0" encoding="UTF-8"?>

<!DOCTYPE bookmap PUBLIC "-//OASIS//DTD DITA 1.3 BookMap//EN" "bookmap/dtd/bookmap.dtd" [

]>

<?Fm ShowAll True?>

<bookmap

    xmlns:ditaarch="http://dita.oasis-open.org/architecture/2005/">

<chapter href="TestConceptOne.xml" keys="TestConceptOne"

    type="concept"><topicmeta><navtitle>Test Concept One</navtitle></topicmeta>

<topicref href="TestTaskOne.xml" keys="TestTaskOne" type="task">

<topicmeta><navtitle>Test Task One</navtitle></topicmeta></topicref></chapter>

<chapter href="TestConceptTwo.xml" keys="TestConceptTwo"

    type="concept"><topicmeta><navtitle>Test Concept Two</navtitle></topicmeta>

<topicref href="TestTaskTwo.xml" keys="TestTaskTwo" type="task">

<topicmeta><navtitle>Test Task Two</navtitle></topicmeta></topicref></chapter>

<chapter href="TestConceptThree.xml" keys="TestConceptThree"

    type="concept"><topicmeta><navtitle>Test Concept Three</navtitle></topicmeta>

<topicref href="TestTaskThree.xml" keys="TestTaskThree"

    type="task"><topicmeta><navtitle>Test Task Three</navtitle></topicmeta></topicref></chapter></bookmap>

[Ashish.K · Accepted solution]

Hi Alex,

As discussed, we have logged a bug# FRMAKER-3728 for this issue. We will try to address this issue in future updates/release of FrameMaker.

Regards

Ashish Kumar