Settings for MIF file type exported from FrameMaker 8-2017 (.mif files).
Common page
Available options are:
- Process reference formats
- Extract cross reference formatting for translation or skip it.
- Process autonumber definitions
- Autonumbering is often used to number pages, chapters, and so on. You can extract for translation the numbers that are produced by autonumbering, or skip them.
- Process element definitions
- Element definitions are used in structured FrameMaker. They are stored in an Elements Definitions Document (EDD). You can extract these element definitions for translation or skip them.
- Process Text Inset content
- In FrameMaker, a text inset is a text element imported by reference. If selected, then element definitions specified in MIF file will be extracted for translation. If not selected, the definitions are ignored.
- Process hidden conditional text
- Hidden conditional text is conditional text that is not exposed in the source document. If processed or extracted, the text is extracted as the subsequent segment. If not processed (not extracted), the text is included as an inline tag.
- Display special characters as text
- Examples of special characters are non-breaking space, tab and discretionary hyphen. You can treat these characters as text or as tags. If you treat them as tags they are put into inline tags. Em dash and en dash are always treated as text.
- Process special formatting
- Special formatting is formatting that cannot be shown in the editor. Examples are:
- Rotation
- Scaling
- Pair kerning
- Spacing
If you choose to process special formatting, such formatting is represented as tags in the target document. If you do not process special formatting, it is lost in extraction.
- Process master pages
- Master pages are one type of FrameMaker page, along with reference and body pages. You can include in the translation or ignore.
- Convert forced line breaks to inline tag
- If you choose this, hard returns (forced line breaks) are converted to tags that appear inside the segments. If you do not choose this, they are converted to
structure tags and so cause a segment break.
- Remove optional (discretionary) hyphens
- The placement of discretionary hyphens is dependent on the structure and pronunciation of words in the source language, so usually you should choose to remove rather than extract them.
- Create segment for each index entry level
- If not selected, index entry characters are extracted as inline tags.
- Exclude index markers from segment boundaries
- Consider setting this if you use SDLX translation memories.
Consider you have a segment with a leading (or trailing) index, such as the following:
<index/> text ... text
If this setting is enabled (that is, index markers are excluded), you get the segment:
text ... text
In SDLX all leading and trailing indexes were excluded from segments.
- Process variables
- You can extract the FrameMaker variables for translation (all variables or just those used). If you do not extract the variables the value of the variables as used in the FrameMaker document is nonetheless extracted for translation.
- Process reference pages
- One type of FrameMaker page, along with master and body pages. You can extract the content for translation of all, some or no pages.