For example, if you move document, project, and FileID files to another folder, Mif2Go still expects to find the FileID file in the original location. This is because the configuration file contains an absolute (full-path) reference to the location of the FileID file at the time the project was created. If Mif2Go does not find a FileID file in the referenced folder, Mif2Go creates a new one there. To get around this problem, edit the configuration file to change the reference; see §C.4 .
You may delete reference (.ref) files as a precursor to a full rebuild. Deleting reference files created in a prior conversion can make the next conversion of the same document run faster. This is safe practice only if both of the following apply:
Otherwise, you might get broken cross references from other files, until you reconvert those files also. If you reconvert only one chapter after deleting .ref files, any cross references from that chapter to other chapters (or HTML split files) will be wrong until those other chapters have been reconverted also. See §C.5 . See also §33.3.3
If you add, rename, or remove any files in your FrameMaker book between conversions, you might need to edit certain conversion files. See §C.4 and §C.5 . To modify a conversion file, use a text editor such as Notepad. Otherwise, do not change the content of any conversion files except for the configuration file, unless you know what you are doing.