Condition Tags

Designer Dialog Box Actions

Formatting Commands

Paragraph Commands

Unify, forced forces the designer to match the selection, and forces all same-named paragraphs to match as well.
Unify, with prompt also forces the designer to match the selection, but also gives you the option of forcing or not forcing other same-named tags to match the selection.

Character Commands

Other Timesavers

Graphics

Indexes

Autocompress. Insert <$autorange> at beginning of the reference-page paragraph that begins with the marker type. For example, edit the paragraph with the tag IndexIX to contain

<$autorange><$pagenum>

Ranges. Need a starting page and an ending page.

<$startrange>configuration

<$endrange>configuration

See and See Also. These usually get special treatment. Sees are frequently the only item in an entry, and see alsos tend to appear as the very first or very last item; this is called the "sort order". For example:

Sort Order. Using brackets, enclose the position at which the entry should be alphabetized.

item:text[aaa]

item:text[zzz]

color:in Acrobat[color:Acrobat]

Turn Off Page Number. Use <$nopage>, described in See and See Also references. It turns off numbers immediately after it occurs; this means you can use it in the middle of a string.

Running Headers and Footers

Headers and Dictionary-Style Headers

You can allow Frame to use more than one paragraph tag by placing each tag in a sequence, separated by commas. Use a plus sign (+) to tell Frame to use the last instance of a tag on a page.

To use the first instance of any tag in the list:

<$paratext[paratag1,paratag2,...,paratagn]>

To use the last instance of any tag in the list:

<$paratext[+,paratag1,paratag2,...,paratagn]>

The previous example is commonly used for the recto page of a book with dictionary-style headers, although you would normally not use a list of tags and would simply use one tag:

<$paratext[+,paratag]>

Using Markers in Headings

To use a marker (instead of a paragraph's contents), use a Running H/F variable that's been defined to look for a marker (for example, Running H/F 3 is predefined as <$marker1>). Then, insert the corresponding marker into the text, taking note that marker definition <$markern> always looks for the marker Header/Footer $n. The table below shows what you would use using Frame's predefined variables and markers:

Special Characters

Elements Used in Regular Typing

All quote codes assume the smart quotes setting is on. In the MIF column, all underscores (_) represent spaces.
In the "In Find Dialog" column, it is understood you can also use the value in the "Hex Code" column as well. Find codes have dependencies on whether smart quotes is enabled, but you can always rely on hex codes.

Why are some missing? Because I used only cross-platform keystrokes. For example, Ctrl+Space is a nonbreaking space in Windows, but not in Macintosh. Escape Space h works in both, so I use only that.

Special Characters Used in Find/Change Dialog Boxes

Spelling

To have FrameMaker use your hyphenation settings, you must first click the "incorrect" word at the top of the dialog box, then click Show Hyphenation.

Other characters you may see in DIC files:

Tables

Standard Line Widths

Table and Cell Actions

Tool Selection

Each "1" is a number 1.