31.4 Using older directive markers for RTF

The directive-marker method described in this section is deprecated; however, Mif2Go continues to support existing uses of this method, for backward compatibility. For new RTF conversion projects, use the method described in §31.2 Overriding settings with markers or macros.

Note: Settings changed via this older method persist for the rest of the FrameMaker file after the point where you insert the directive marker.

Mif2Go commandeers one of the FrameMaker marker types for RTF directive markers. By default Mif2Go uses the Comment marker for this purpose:

[Options]

; DirectiveMarker = marker type for DCL use, default 3 (Comment)

DirectiveMarker=3

FrameMaker 5.5.6 and later versions do not list marker types by number in the Marker dialog, numeric designations above 11 are no longer consistent across FrameMaker versions, and there is no easy way to determine the number that corresponds to a given marker type. Therefore, you can no longer designate another marker type for this purpose.

To change the value of a configuration setting partway through your document, insert a FrameMaker marker of the type specified by the value of [Options]DirectiveMarker at the place where you want the setting to change, and supply the following content for the marker:

X:filename.ini [Section] Key=NewValue

where:

X:	is an optional scope prefix
filename	is drmif, dwrtf, or mif2rtf, depending on the directive
Section	is the name of the configuration-file section where the setting belongs
Key	is the name of the keyword whose value you want to change
NewValue	is the new value for that setting.

Spaces around [Section] are optional.

For example, this marker:

G: drmif.ini [Graphics] UseFrameImage=Yes

says to use the FrameImage facet (if present) of all following graphics in preference to any other facets, until another directive changes that value:

G: drmif.ini [Graphics] UseFrameImage=No

You can use this marker facility to change settings (for predefined key names) anywhere in your document, as many times as necessary.

Scope prefix

The scope prefix in a directive marker can have the following values:

G:	for graphics (affects the next anchored frame and all thereafter)
F:	for file settings that affect the entire file, regardless of marker location

File name

filename can have the following values:

drmif	Affects the operation of the following Keys in these Sections: [Options] OutputType, ObjectIDs, XrefType, DirectiveMarker, ImportGraphics, EpsiUsage [Graphics] UseFrameImage
dwrtf or mif2rtf	Affects Keys in these Sections: [Defaults], [Options], [Tables], [Graphics], [GraphFiles], [Fonts], [FontWidths], [FontTypes], [Styles], [HelpTags], [HelpData], [HelpBrowse], [TextFlows], [RefFrameFormats], [XrefFiles], [WordOptions], [HelpOptions]

Keyword

For dwrtf and mif2rtf, specific Keys are affected in the following Sections:

[Options] and the other [*Options] sections (based on Output):

GraphText, FilePaths, FileNames, Metafiles, OccludedTabs, EmptyFrames, SHVertAdjust, RefFrameFormat, FrameStyle, UseParaAnchors

[Tables]

TableTitles, TableRules, TableFill, TableGraphics, TableRuleAdjust, StripTables, TableWidthsFixed

[Graphics]

GraphText, FilePaths, FileNames, Metafiles, BackMode, StretchMode, BitmapDPI, BitmapFlip, TextScale, TextWidth, ClipText, ClipType, ClipLimit, GrVertAdjust, GrTableSpace, FrameExactHeight, UseTopSpaceAbove, NoBlankFirstGTLine, WrapAllFrames, EmbedBMPsInWMFs

[HelpBrowse]

TitleBrowse, Start, Step, Digits, Prefix

Keys that have names that are not predefined, such as font and format names, are ignored; you cannot use marker directives to change their values.

New values for settings

Boolean NewValues are evaluated as follows:

True	NewValues "yes", "true", and "1" (case insensitive)
False	All other NewValues

This is more limited than the regular Boolean checking rules Mif2Go applies.

 

---

> 31 Overriding configuration settings > 31.4 Using older directive markers for RTF