Omni Systems, Inc. Mif2Go User's Guide, Version 55
> 29 Working with FrameMaker markers > 29.4 Defining and redefining marker behavior > 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:
; 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[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
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. |
||
Any macros in the marker are expanded, and the
content is surrounded by any code specified for the marker type in |
||
Content is a configuration setting of the form
|
||
The marker is removed entirely; Mif2Go applies this property last, after any other properties you specify. Must be specified last. |
||
Content is a configuration setting of the form
|
||
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. |
||
Each of these markers has the same effect as
the corresponding |
||
|
||
|
||
Marker content names the current split or extracted file; dangerous (see §34.8.3 Using custom markers to name output files) |
||
Marker content specifies another help file to be merged at the point of insertion |
||
Content is a configuration setting of the form
|
||
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. |
||
Marks a split point in a FrameMaker file; has the same effect as |
||
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 |
||
Marker content becomes the page |
||
Same as the |
||
HTML Help only. Marker content names a secondary window as the target for jumps from the paragraph containing the marker. |