(register)   username:   password:  

Community KB :: DITA / FrameMaker

A collection of tips and troubleshooting information. Feel free to register and add your own items.

Tags:                                        
Keywords: 

FMN DITA .. refers to the DITA support that is provided by default in FM9 and FM8.

DITA-FMx .. is a plugin that provides extended DITA authoring support for FM9, FM8, FM7.2 and FM7.1. More info...

Submitted by: Roger Shuttleworth (2011-05-04)

TAGS:  Output, FM9 DITA, FM 9.0
SUMMARY:  Related links are absent from FrameMaker output, or point to XML files.
ISSUE:  When converting a ditamap to FM in FM9.0, the topic references stored in relationship table rows do not generate related-links sections of the output; or if they do, the links point to XML files instead of FM files.
SOLUTION:  A. Related links are absent altogether.

(a) This may result if the ditamap has extra metadata elements in it. Such elements may be added if you open the ditamap in applications other than FrameMaker. For example, the IBM Information Architecture Workbench adds metadata elements before and within the relationship table. Delete these extra elements after opening the ditamap in FrameMaker.

(b) FrameMaker 9.0 DOES NOT process relationship tables that are in nested maps. Use relationship tables in the container map only. FrameMaker DOES create related links from topicrefs that reference topics nested in sub-maps, but only if the relationship table is in the container map.

B. Related links point to XML files instead of FM files.

(a) If you are using an Übermap referencing *only* sub-maps, save the ditamap as a FM9 book with
components. If the map contains *only* straight topicrefs, save it as a composite document. That way, all your related-links will point to the correct .fm files or IDs, and not to the original XML files.

(b) If you mix straight topicrefs AND sub-maps in the same Übermap, the related links are output as follows:
   (i) If you save as a FM9 book with components, the links between the straight topicrefs reference .xml files (bad), while links between topics within the sub-map reference .fm files (good).
   (ii) If you save as a composite document, all the links are OK (pointing to FM IDs).
So mixing is obviously not the way to go unless you want to create a single, composite FM document as output. OK for drafts, maybe.

(c) If you have an Übermap with a straight topicref and a sub-map, and a reltable that links the topicref with one of the topics in the sub-map, the related-links come out OK - but only if you save as a composite FM document (as above).

The safest course is therefore to use sub-maps and save as a FM book.