Skip to main content
A
Anonymous
February 23, 2010
Answered

Composite Books from DITAmap - Load xref

  • February 23, 2010
  • 2 replies
  • 1805 views

When building a composite book with FrameMaker documents, and have the Auto Load XREF checked, resolves the cross references to the dita topics, instead of the fm documents. As a fm book with fm documents is built, the cross references are expected to point to fm documents, not dita/xml files.

Is this a bug, or is there a way to have the cross references point to the generated fm files?Failing to point to the fm location causes cross reference problems when publishing to PDF as all links will be broken.

The Save Ditamap as book will generate a book with dita topics and is therefore references are assumed to point to xml/dita files.

This topic has been closed for replies.
Correct answer TarunGarg_TG_

When using "File->Save Ditamap As - Book With fm components", the xrefs in the generated book refer to the corresponding fm document and not the original xml/dita file. Hence, the links in PDF also get generated properly.

In case, it is not happening this way at your end, then there seems to be some specific reason.

I will suggest you to try the following steps:

1) Create new Map.

2) Create two new topics - 1.dita & 2.dita - and add to map.

3) Add an xref in 2.dita pointing to an element in 1.dita.

4) Save as Book with fm components

5) Open 2.fm book component.

6) "Double click" on the xref. The DITA xref dialog shall display 1.fm as the source file name.

Also, what version of FM are you using ? (to check this use "Help->About FrameMaker")

Regards,

Tarun Garg

tarung@adobe.com

Adobe FrameMaker Engineering

2 replies

X
xml_guru
Participant
March 13, 2010

I have the same thing happening on several machines. It can't be a corrupted FM installation. There must be a setting somewhere

creating this problem. I need this to work. Our DITA implementation hangs in the balance.


A
Anonymous
March 18, 2010

After some testing, I have found out that patch p250 (latest patch; upgrade from patch p237) in FrameMaker 9 introduced this bug in the DITA implementation.

Prior to this patch, when saving the ditamap as a Book with fm components, the cross references are correctly resolved to the FrameMaker documents created during this process. Once this patch is installed, the cross references are no longer resolved to the fm documents, but to the source dita topics.

A temporary solution would be to uninstall patch 250 via the control panel.

T
TarunGarg_TG_Correct answer
Participating Frequently
February 23, 2010

When using "File->Save Ditamap As - Book With fm components", the xrefs in the generated book refer to the corresponding fm document and not the original xml/dita file. Hence, the links in PDF also get generated properly.

In case, it is not happening this way at your end, then there seems to be some specific reason.

I will suggest you to try the following steps:

1) Create new Map.

2) Create two new topics - 1.dita & 2.dita - and add to map.

3) Add an xref in 2.dita pointing to an element in 1.dita.

4) Save as Book with fm components

5) Open 2.fm book component.

6) "Double click" on the xref. The DITA xref dialog shall display 1.fm as the source file name.

Also, what version of FM are you using ? (to check this use "Help->About FrameMaker")

Regards,

Tarun Garg

tarung@adobe.com

Adobe FrameMaker Engineering

A
Anonymous
February 23, 2010

I tested it as per your instructions in the Default structapps setting (so used DITA-Topic-FM and DITA-MAP-FM) within FM9.0p250.

  1. Created a book (Test.book)
  2. Created 2 topics (test1.dita and test2.dita)
  3. Used fm-xref to insert a reference from test2.dita to the topic of test.dita).
  4. Saved files
  5. Selected File > Save Ditamap As... Book 9.0 with fm components
    6. Book and fm files were created.
  6. Opened test2.fm
  7. Held CTRL+ALT and selected the link
  8. test.dita is opened (I expected test.fm to open instead)
  9. In test2.fm, double-clicked on the reference.
    source file is test.dita, not test.fm

Regards,

Ferry van der Vorst

ferry.van.der.vorst@mekon.com

A
Anonymous
March 4, 2010

It appears the installation of FrameMaker 9 was corrupted. On other machines it worked OK.

Terms & ConditionsAccessibility statement
Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices