2.2 Naming FrameMaker formats
Mif2Go does not impose restrictions on FrameMaker format names. However, your conversion projects might go more smoothly if you adhere to the following guidelines. Avoid using format names that:
• are identical for a paragraph format and a character format
• differ only in case (such as Body and body)
• contain punctuation or other non-alphanumeric characters.
Paragraph and character format names should differ
Using the same name for a paragraph format and a character format can cause problems, unless you are careful to specify properties for those formats in the correct configuration section; see §21.5 Assigning properties to text formats. Even then, if you use any characters in symbol fonts, those characters might be incorrectly mapped. Mif2Go writes a warning to the log file if your FrameMaker document uses the same name for both a character and a paragraph format.
Do not rely on difference in case
A common issue is using (for example) both Bulleted and bulleted as paragraph format names, with different definitions. This is valid in FrameMaker, but nowhere else, because most other programs—including browsers that process CSS, and Microsoft Word—do not consider a difference in case alone to constitute a difference in identity. These are not just issues for Mif2Go, but for the downstream software that must interpret the results of your conversion. Mif2Go writes a warning to the log file if your FrameMaker document uses format names that differ only in case.
The characters “=”, “;”, and “[” must be escaped with a backslash when a format name is referenced in a Mif2Go configuration file.
Eschew wildcard characters in names
It is best not to use wildcard characters “*” and “?” in any names. However, you can turn off wildcard use (and turn on case sensitivity) if you need to accommodate formats with such names. See §5.1.7 Specifying how to treat cases, spaces, and wildcards for more information.
Spaces in format names can be a problem for HTML
Spaces in format names are harmless if you are converting to RTF. If you are converting to HTML, spaces are a problem only if you have two format names that become the same when spaces are removed (which is required for CSS). For example, if your document uses both heading 1 and heading1, there will be a conflict in the CSS file. Mif2Go writes a warning to the log file if your FrameMaker document uses format names that contain spaces, and removing the spaces results in duplicate names.
> 2 Planning a conversion project > 2.2 Naming FrameMaker formats