29.4.3 Understanding examples of marker redefinition
Check the following examples for ways to use redefined markers:
Example: redefining Subject marker type
Example: extracting content from markers
Example: combining Split and FileName properties
Example: redefining HTML Macro marker type
Example: redefining Subject marker type
You could redefine the behavior of the original Subject marker type in the example in §29.3 Remapping marker types and hypertext commands so that after remapping Subject markers, the original Subject markers could be used to mark split points instead. You would specify:
Subject = Index ALinkRef Subject
Or, you could simply specify Split as a marker type on the right in [Markers]:
Subject = Index ALinkRef Split
This works because when you give a marker type the same name as a property, Mif2Go takes that as an implicit request to use that marker type to assign that property. In effect, each [MarkerTypes] property name can also be used as the name of a predefined marker type. See §29.6 Using marker property names for marker types for more information.
Example: extracting content from markers
To roll your own macros for related-topic buttons in HTML Help, you could capture ALink keywords from Subject markers, remap Subject markers to a new marker type, and also clone the resulting markers:
See §9.7.5.2 Creating a list of ALink keywords from markers for a description of how these markers and their contents can be used to build button macros.
Example: combining Split and FileName properties
As another example, you can combine Split and FileName properties in one marker type, as follows:
1. Add a new custom marker type in FrameMaker, called (for example) SplitFile.
2. Make the content of each SplitFile marker the base file name (no extension).
3. Specify the following setting for the SplitFile marker type:
Example: redefining HTML Macro marker type
You cannot specify both HTMLComment and Code properties for the same marker type. However, you can specify both as marker types in [Markers], and each will have its usual effect. You might want to do this, to include as a comment the macro that will be expanded in the HTML code. This can help when you are setting up a macro system where macros call other macros; you can see what you asked for, and what you got.
To make each FrameMaker HTML Macro marker into a custom HTMLComment marker, plus a custom Code marker, with macro expansion:
> 29 Working with FrameMaker markers > 29.4 Defining and redefining marker behavior > 29.4.3 Understanding examples of marker redefinition