## 34.8 Renaming output files for automated systems

For names of Mif2Go-generated files, Mif2Go is more restrictive than Windows. Only alphanumeric characters and upper-ASCII accented characters are allowed; no punctuation at all (except a leading underscore for starting topic files), and no spaces, unless you explicitly override these restrictions. See §1.1.2 File, directory, and path names.

The ability to respecify output file names is available for a single purpose: to allow creation of files that external software tools need to have named a particular way. Doing so works well for that purpose. Do not try to rename split files unless you are constructing an automated system. Why? Because our experience shows there is a very high probability of name collisions.

Note: Renaming an output file outside of Mif2Go breaks any links to that file; however, see §19.6.4 Enabling links to renamed or relocated files.

In this section:

§34.8.1 Understanding which files can be renamed

§34.8.2 Renaming individual output files

§34.8.3 Using custom markers to name output files

§34.8.4 Using paragraph formats to name output files

§34.8.5 Including identifiers and sequence numbers in file names

| 34.7 Converting autonumbers for database systems |  | 34.8.1 Understanding which files can be renamed |