4.1.5 Specifying file paths in configuration settings
Path and file names must conform to the requirements listed in §2.1 Naming files, folders, and paths, otherwise you risk run-time errors. Additional considerations:
Path separator can be "\" or "/" except sometimes
Paths with spaces must be quoted
Relative paths relate to the project folder
Path separator can be "\" or "/" except sometimes
When you specify a file path in a configuration setting, you can use either a backslash "\" or a forward slash "/" as a separator character. A forward slash is preferred, except in the following cases, where you must use a backslash:
• system commands; see §32.4.2 Executing system commands before and after conversion
• command parameters; for example, see §33.9 Archiving deliverables.
In dialogs, the backslash has a special meaning that trashes paths beyond recovery. In Windows API calls, forward slashes work fine, because the original Windows programmers compiled Windows on VAX/VMS machines.
Paths with spaces must be quoted
If a path contains any spaces, enclose the entire path in quotes. See §2.1 Naming files, folders, and paths and §3.1 Checking set-up and conversion requirements.
Relative paths relate to the project folder
Most path settings in the configuration file can be either relative or absolute. When you specify a relative file path in a configuration setting, the path is relative to the value of [Automation]WrapPath, which is in turn relative to the project folder. If no setting for WrapPath is present, all relative path values are relative to the project folder. See §33.4 Assembling files for distribution.
> 4 Setting configuration options > 4.1 Editing a Mif2Go configuration file > 4.1.5 Specifying file paths in configuration settings