C.5.1 Understanding how reference files work
When Mif2Go encounters in one FrameMaker file a cross reference or link to another file in the document, Mif2Go looks for the reference file produced when that other file was processed—even if that other FrameMaker file is in a different directory. If the reference file is present, Mif2Go uses the information it contains to create a link to the correct split part of that other file.
When Mif2Go encounters, in the reference file for the current FrameMaker file, a marker for a cross reference from another file, Mif2Go updates the other file to point to the correct split part of the current file. The net effect is that after Mif2Go processes the last file in a document, all links between all files are correct.
During conversion, Mif2Go updates HTML files that are already in the project directory if they contain links to FrameMaker files that Mif2Go has not yet processed; and if those FrameMaker files are then split, the links in the HTML output files are updated to point to the correct split parts. This means you must leave all HTML files in the project directory until the entire conversion is finished.
Reference files are fully regenerated only when you convert the entire document they deal with, along with any other files that reference, or are referenced by, files in that document. Until you complete the conversion, some of the links to files that are split will be wrong. The HTML output files might also be updated as part of the process, and must be left where created for this to work.
If you find an entry followed by a double asterisk in a reference file; for example:
ca871052=49CFR191.htm#Xbw1006201 **
The double asterisk means that Mif2Go was unable to resolve the reference. See §D.2.7 Check for broken links (HTML or XML output).
> C Document and conversion files > C.5 Working with reference files for HTML or XML > C.5.1 Understanding how reference files work