## 29.1 Using custom FrameMaker markers

You can add custom marker types in FrameMaker, and use configuration settings to define the behavior of markers of those custom types in Mif2Go conversions. You can also redefine the behavior of existing marker types and hypertext commands.

You can do the following with FrameMaker markers:

• Add custom marker types. Mif2Go uses custom markers to produce predefined effects; see §29.2 Adding custom marker types.

• Invent new marker types, and assign properties to them; see §29.3 Remapping marker types and hypertext commands.

• Remap most marker types, and optionally give them new properties; see §29.3 Remapping marker types and hypertext commands and §29.4 Defining and redefining marker behavior.

• Redefine the behavior of most marker types; see §29.4 Defining and redefining marker behavior.

• Map custom markers directly to Hypertext marker subtypes (hypertext commands); see §29.3 Remapping marker types and hypertext commands.

For example, you can use custom markers to do any of the following:

• Designate split points and extract extents for HTML (see §18.2.1 Designating split points).

• Insert WAI markup (see §25 Generating WAI markup for HTML).

• Provide ALink entries for Help systems (see §7.6 Providing related-topic links for Help systems).

• Identify context-sensitive help targets (see §7.10 Setting up Context Sensitive Help (CSH)).

• Assign alternate configuration values to individual tables, graphics, paragraphs, or character spans (see §33.2.2 Overriding settings with configuration markers).

• Add links and instructions (§34.1.2 Using markers to add links and instructions).

See also:

§5.11 Repurposing FrameMaker markers

| 29 Working with FrameMaker markers |  | 29.2 Adding custom marker types |