Mif2Go User's Guide: 29.4.1 Assigning properties to marker types

29.4.1 Assigning properties to marker types

You can define the behavior of a new marker type, or redefine the behavior of an existing marker type, by assigning one or more properties to the marker type:

[MarkerTypes]

; marker type name = properties

FM_Marker = Property1 Property2 ...

Most properties are specific to HTML or to RTF

Which properties you can assign depends on whether you are converting to HTML or to RTF. A few properties are common to both output types: Delete, Code, ALink, and Config. The rest are specific to either HTML or RTF output. Table 29-3 lists all the [MarkerTypes] properties, shows which output types apply, and describes the effect of each property.

Marker types lose original properties

When you assign properties to a FrameMaker marker type in [MarkerTypes], that marker type loses its original FrameMaker functionality; instead, it takes on the properties you assign to it.

Marker types remapped in [Markers] are gone

If you remap a marker type to something else in [Markers], unless you also remap that type to itself, Mif2Go ignores [MarkerTypes] property assignments to the original marker type. In fact, for conversion purposes, the original marker type is gone. However, Mif2Go does honor [MarkerTypes] property assignments to any new marker types you define in [Markers]. See §29.3 Remapping marker types and hypertext commands.

Table 29-3 Effects of [MarkerTypes] properties

Output	Property	Effect
RTF or HTML	ALink	Content is treated as a list of names of categories that apply to the current topic. Category names should be single terms, separated by semicolons. Use spaces or other punctuation in the names at your own risk. Available for WinHelp, MS HTML Help, OmniHelp, and Oracle Help for Java.
	Code	Any macros in the marker are expanded, and the content is surrounded by any code specified for the marker type in [MarkerTypeCodeBefore] and [MarkerTypeCodeAfter]; see §29.7 Inserting code or text with markers for more information. Cannot be combined with HTMLComment. Compare with property Text for generic XML or HTML/XHTML output.
	Config	Content is a configuration setting of the form [Section]Key=Value or [Section]=Value; see §33.2 Overriding settings with markers or macros.
	Delete	The marker is removed entirely; Mif2Go applies this property last, after any other properties you specify. Must be specified last.
RTF only	RTFConfig	Content is a configuration setting of the form [Section]Key=Value or [Section]=Value; see §33.2 Overriding settings with markers or macros.
HTML only	ANSI	Specifies the Windows code page to use for FrameMaker, default 1252; or 1250 for CE/EE, 1251 for Cyrillic, 1253 for Greek, 1254 for Turkish. See §13.4.3.2 Selecting a Windows code page for single-byte character sets.
	Extr*	Each of these markers has the same effect as the corresponding [HTMLParaStyles]parafmt=Extr* property; see §18.3.1 Enabling and disabling extract processing. For ExtrDisable, ExtrEnable, ExtrEnd, and ExtrStart, any content is ignored, unless you also specify other properties that use the content, such as Code.
	ExtrBottom	Content becomes the last item in the extract <body>.
	ExtrDisable	Turns extract processing off.
	ExtrEnable	Turns extract processing on.
	ExtrEnd	Ends a file extract, but is not part of the extract.
	ExtrFinish	Ends a file extract, and is the last part of the extract.
	ExtrHead	Content is placed in the <head> of the extract, after the <title> element.
	ExtrReplace	Content replaces an extract in the parent file.
	ExtrStart	Begins an extract. Must be specified before FileName or Title.
	ExtrTop	Content becomes the first item in the extract <body>.
	FileName	Marker content names the current split or extracted file; dangerous (see §34.8.3 Using custom markers to name output files)
	HelpMerge	Marker content specifies another help file to be merged at the point of insertion
	HTMConfig	Content is a configuration setting of the form [Section]Key=Value or [Section]=Value; see §33.2 Overriding settings with markers or macros.
	HTMLComment	Marker content is treated as an HTML comment, and enclosed within HTML comment delimiters; or, if you specified XML as the output type, marker content is properly converted to an XML comment. Cannot be combined with Code.
	Split	Marks a split point in a FrameMaker file; has the same effect as [HTMLParaStyles]parafmt=Split; see §18.2.1 Designating split points. Any content is ignored, unless you also specify other properties that use the content, such as Code. Must be specified before FileName or Title.
	Text	Marker content is processed as pure text per the current text encoding rules; non-alphanumeric characters are treated as text and properly encoded for output. Applies to generic XML and HTML/XHTML output only; see §29.7.3 Processing marker content as text for XML/HTML/XHTML. Compare with property Code.
	Title	Marker content becomes the page title attribute of the current split or extract file.
	TopicStartCode	Same as the Code property, except macros are expanded at the start of the topic. Any output the macros create is available as predefined macro <$_TopicStartCode>, which can be used anywhere in the current topic.
	Window	HTML Help only. Marker content names a secondary window as the target for jumps from the paragraph containing the marker.

> 29 Working with FrameMaker markers > 29.4 Defining and redefining marker behavior > 29.4.1 Assigning properties to marker types

Mif2Go User's Guide: 29.4 Defining and redefining marker behavior

Mif2Go User's Guide: 29.4.2 Observing restrictions on redefining marker behavior