5.1.5 Checking for broken links in HTML or XML output
When you convert a FrameMaker book to HTML or XML, Mif2Go can check all the interfile cross-reference and hypertext links in your output, and provide a FrameMaker “Book Error Log” that lists any broken links.
Note: Although this feature is not available for RTF, MIF, or DCL conversions, you can still check links for those outputs by running an HTML conversion on the same book, with the same conditions shown. The same link errors should be found.
; CheckLinks = No (default) or Yes (check links after running a book)
; CheckLinkLog = D:\path\to\LinkLog.fm to make copy of Book Error Log
CheckLinkLog = path\to\MyBadLinks.fm
; LinkLogAlways = Yes (default) or No (do not display Book Error Log
; if no broken links are found)
When CheckLinks=Yes, after converting a book, Mif2Go writes a notice to the FrameMaker Console window showing how many broken links were found. If Mif2Go finds at least one broken link (or if LinkLogAlways=Yes), Mif2Go displays a Book Error Log in FrameMaker, and closes only those FrameMaker files that have no link errors. The Book Error Log contains active links to the broken links in the open files.
To save the Book Error Log, assign an absolute path and file name to CheckLinkLog. Mif2Go copies the Book Error Log to the specified file for safekeeping; the Book Error Log itself disappears when you exit FrameMaker.
If Mif2Go finds more than 1,024 link errors, only the first 100 are logged. This indicates a massive problem, for which additional information from the other 924+ errors would not help.
In a few cases you might find that an interfile link reported by Mif2Go as broken actually works just fine in FrameMaker. This can happen when macros are involved, or can be caused by latency issues in Windows shell operations. The remedy is to re-convert the chapter containing the link, without deleting any .ref files.
> 5 Setting basic conversion options > 5.1 Specifying operating settings > 5.1.5 Checking for broken links in HTML or XML output