There are two ways to resolves external links. If you create external links by using the link database feature, Doc-O-Matic processes them just as native links and verifies them during the generation process. But Doc-O-Matic does not verify "real" external links. Therefore, you must make sure that the target is valid and that links in the created format can go to such targets.

All topic IDs you use as native targets must either be in your current project or in a Doc-O-Matic link database. Add link databases on the Project Manager to your project. For more information about how to use the link database feature in the Topic Editor, see Using Link Databases.

You do not need a link database prefix when you are generating HTML Help files. When you are generating multiple cross-linked HTML Help projects, you need to store output files in the same folder. For example, when you create a HTML Help file, which links to the MFC documentation, you must copy the generated CHM (and .CHI) files to the same folder in which the MFC HTML Help files are located. 

The exporter for HTML Help resolves links automatically.

In Help 2 namespaces are used to identify each project. You must not store projects that link to each other in the same folder.

You can determine whether link database links are resolved before native links or after them on the Project Database page. Doc-O-Matic attempts to detect real native targets first and then it attempts to detect targets in all link databases by default.

PDF settings apply to: Doc-O-Matic Professional and Doc-O-Matic Author