6.17.2 Including index terms in Word
To have Mif2Go include index terms in RTF output:
; Index = Standard (Word index markers), or None
When Index=Standard, Mif2Go creates a Word {xe} field for each index marker. This happens whether or not you also convert a FrameMaker index, which does not use {xe} fields for index references.
Note: Word uses the character formatting in effect at the {xe} field itself for the entire index item. To avoid unwanted formatting, place index markers at the very end of a paragraph. (Or at the very beginning; though if the paragraph format itself includes bold or italic, those effects will apply to the index item.)
When Index=None, Word {xe} fields are not created.
See also” type index references are not supported by Word index generation, and Word has no concept of omitting page numbers from the indexes it produces.Mif2Go cannot prevent the bogus page number in a <$nopage>see-also index link from appearing in a Word-generated index, because Word has no field switch for that purpose. However, when you specify Index=Standard you can direct Mif2Go to refrain from converting <$nopage> index markers to Word {xe} fields:
; NoSeeAlso = No (default, keep See Also markers)
When NoSeeAlso=No, <$nopage> index markers are converted to {xe} fields in RTF output files. When you generate an index in Word, unless you used IndexRef before converting (see §5.5.4 Making See and See also index entries into useful links), the corresponding entries appear with links to the pages where the {xe} fields are located: bogus references.
When NoSeeAlso=Yes, <$nopage> index markers are not converted to {xe} fields in RTF output.
This option has no effect on indexes that Mif2Go converts to Word from the FrameMaker IX file; see §6.12 Converting generated files to print RTF.
> 6 Converting to print RTF > 6.17 Managing Word output after conversion > 6.17.2 Including index terms in Word