Your contact

Nachfolgender Link öffnet ein Pupup-Fenster für diese Website.Klaus Müller

+49 (0)89 892623-660

Convert: FM to MIF / MIF to FM

FM2MIF2FM.fso

Problem description

During the translation process, FrameMaker documents must be saved to MIF and the translated MIFs must be converted back to the FM format.

FrameMaker does not offer the option to convert all documents of a book into MIF. This option is only available for individual documents.

Function description

The script converts the current document, all documents of the current book or all open documents into MIF.

MIF documents in a folder to be selected will be converted to the FM format. Optionally, the MIFs in subfolders can also be saved in the FM format.

The commands are available through the file menu in addition to the [i]-frame menu. In accordance with the FM commands to save documents and books, the script commands in the file menu depend on the status of the Shift key prior to clicking on the menu:

  • Shift key is not pressed: Saving the document or book as MIF
  • Shift key is pressed: Saving all open files or all files of the book as MIF

To convert MIF documents into FM, select the ‘Convert:MIF to FM (folder)’ menu entry where a subsequent dialog will then ask you to select a folder. The folder of the active document or book is the start folder of this dialog.

Because of the limitations of the dialog for folder selection (including specified start folder does not support External link. Target opening in new windowActiveDirectory) a standard dialog to select a file will appear here instead. The selected/specified file name is not taken into consideration here. The selected directory is the deciding factor.

To top

FrameMaker versions (saving as MIF)

Depending on the current FrameMaker version, different script commands will be available indicating the MIF version to which the FM documents can be saved.

  • In FrameMaker 7, only the ‘Save ... as MIF’ command is available.
    The documents are saved as MIF Version 7.0. This document can generally also be opened with earlier FrameMaker versions.
  • In FrameMaker 8, the commands ‘Save … as MIF’ and ‘Save … as MIF 7.0’ are available.
    • When saving as ‘MIF’, the documents will be saved in the current Unicode compatible ‘MIF 8.0’ format.
      Translation memory systems will output these documents in Unicode format after the translation, which means that when Unicode fonts are used and the translated documents are then opened with FrameMaker 8, no adjustment of the fonts is necessary after the translation.
      These MIF documents can also be opened with FrameMaker 9.
    • When saving as ‘MIF 7.0’, the documents will be saved in an older format, which is not Unicode compatible.
      If the fonts that are used in the FM8 documents have the same assigned virtual fonts that are required in FM7 to be able to display the characters from other code pages, no data will be lost (ideally) (e.g.: ‘Arial Greek’ for characters of the Greek Unicode range).
      Translation memory systems also output these documents after the translation in the old non-Unicode compatible FM7 format again.
      Use this format only when you are certain that the documents are not to be processed with newer FM versions (but only FM7 or earlier) after the translation. When converting foreign language documents (from other code pages), make sure that the FM7 compatible virtual fonts have been assigned.
      Note:
      When opening foreign language FM7 documents (from other code pages; FM or MIF) with FrameMaker 8 that use virtual fonts, the characters will be converted to the applicable Unicode characters.
      With FrameMaker 9 this only works with version 9.0p250 (=9.03) and later.
  • In FrameMaker 9, the ‘Save … as MIF’ and ‘Save …as MIF 7.0’ commands are also available.
    FrameMaker 9 does not support the save process in MIF Version 8.0.
    MIF Version 9 is broadly compatible with MIF Version 8.
    Warning: When the documents utilize FM9-specific functions (e.g. the new variable building blocks <$section> and <$subsection>, the corresponding ‘Section’ and ‘Subsection’ numbering settings and the new grouping options in the book), the documents should exclusively be processed in FrameMaker 9.
    • When saving as ‘MIF’, the documents will be saved in the current Unicode compatible ‘MIF 9.0’ format.
      Translation memory systems will output these documents in Unicode format after the translation, which means that when Unicode capable fonts are used and the translated documents are then opened with FrameMaker 8 or 9, no codepage-specific adjustment of the fonts is necessary after the translation.
      No updated FM9 filters of the TM applications were available at the time this manual was released. Therefore, you may receive a corresponding error message when importing FM9 MIFs to your TMS. A sufficient workaround in this case may be changing the version information on the first line of the MIFs globally to ‘<MIFFile 8.00>’ prior to importing the MIFs, into Trados, for example.
    • When saving as ‘MIF 7.0’ the same applies as described above when saving with FrameMaker 8.
      Note:
      When opening foreign language FM7 documents (from other code pages; FM or MIF) that use virtual fonts with FrameMaker 9, it will convert the characters only with version 9.0p250 (=9.0.3) and later into the applicable Unicode characters!

To top

Requirements

  • FrameMaker 6.0 or higher
  • FrameScript/ElmScript 4.1 or higher

Note

The script works with structured and unstructured documents.

To top