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

> 19 Creating HTML links > 19.6 Linking to other files and other Mif2Go projects > 19.6.5 Updating links between files in different projects

### 19.6.5 Updating links between files in different projects

For each FrameMaker file, Mif2Go requires both the corresponding .ref file, and all the .htm files produced from that FrameMaker file, to reside in the same directory as the .ref file itself. Then when you convert a different book, and links from an external file change because a split name changed, Mif2Go updates the files of the referencing book at the same time as the referenced book. This way you do not have to reconvert the other books.

However, if you are using wrap directories (see §35.6 Assembling files for distribution), you do have to copy the changed files from their project directories to the corresponding wrap directories. Mif2Go does not copy the changed files to the wrap directories for the other books. To automate this process, create a .bat file that copies all the output files of all the books to their final destinations, and run that as a SystemEndCommand (see §34.4 Executing operating-system commands) whenever you rerun any book in the group. Copying the files should take only a few seconds to run.

> 19 Creating HTML links > 19.6 Linking to other files and other Mif2Go projects > 19.6.5 Updating links between files in different projects

| Mif2Go User's Guide: 19.6.4 Enabling links to files in other projects |  | Mif2Go User's Guide: 19.6.6 Mapping links to text insets |