Omni Systems, Inc. Mif2Go User's Guide, Version 55

<< Prev | Next >>

> D Technical support for Mif2Go > D.2 Things to check first > D.2.7 Check for broken links (HTML or XML output)

### D.2.7 Check for broken links (HTML or XML output)

When you produce HTML or XML output from a FrameMaker book with CheckLinks=Yes (see §5.1.5 Checking for broken links in HTML or XML output), you might get an error message about broken links. If Mif2Go is unable to resolve any interfile links in your document, you will see a FrameMaker Book Error Log at the end of processing, and the FrameMaker console report will list the number of broken links.

Check ObjectIDs setting

Assuming you were able to successfully update the book before starting Mif2Go, one possible problem might be the following setting:

[HTMLOptions]

ObjectIDs = Referenced

If this setting is included in your project configuration file or in a referenced configuration template, change or override the setting as follows:

[HTMLOptions]

ObjectIDs = All

See §19.5.3 Including ObjectID anchors as link targets. If you are converting generated files, see also §13.8.2.2 Including paragraph references.

Convert again, retaining .ref files

In a few situations you might have to run a conversion twice (without deleting .ref files in between runs) before all links are resolved. The first pass creates or updates the necessary .ref files, and the second pass accesses the link information in those files. See §C.5 Working with reference files for HTML or XML.

Check for relative vs. absolute paths

If links work locally but not when you move all the output files to another location, check whether your project includes any [XrefFiles] settings that specify absolute paths. These settings must specify relative paths; otherwise the links work only on the system where you ran the conversion. See §19.6.3 Enabling links to renamed or relocated files.

No broken links, and the problem still exists? Next: Restart FrameMaker, reboot system.