Skip to main content
skilled_socialite154A
skilled_socialite154A
Participating Frequently
September 21, 2020
Question

Viewing multiple languages in FM 2019 32-bit

  • September 21, 2020
  • 1 reply
  • 481 views

My translator sent mif files to me with a Russian translation of English text I sent to him. He uses either FM 2017 or 19t and I have FM 2019 32-bit.

 

The font he is sending is in the expected Verdana font with the language set to Russian. However, I don't see the Russian characters, rather a set of symbols. When I try to change the language to a different language, including English, the same set of symbols appear.

 

Is there a solution to this issue?

    This topic has been closed for replies.

    1 reply

    S
    Community Manager
    Stefan GentzCommunity Manager
    Community Manager
    September 21, 2020

    Please open the MIF file you got from the translator. For 2017 and 2019, it should read:

    <MIFFile 2017> # Generated by FrameMaker 2017

    or

    <MIFFile 2019> # Generated by FrameMaker 2019.

     

    Does it say that? If it says <MIFFile 7.00>, the problem is, because your translator saved them in an old MIF format from before Unicode times and need to resave the file as FrameMaker 2019 MIF. 

    See also this thread: https://community.adobe.com/t5/framemaker/problem-displaying-chinese-mif-files-from-memoq/m-p/11319102?page=1

     

     

      Bob_Niland
      Community Expert
      Bob_NilandCommunity Expert
      Community Expert
      September 22, 2020

      re: If it says <MIFFile 7.00>

      If it says that, the font model/coding destruction is apt to be far from the only damage done to file content, and probably needlessly.
      MIF 2020, 2019, 2017, etc. can be opened by any FM back to 8.0.

      Anyone saving back to pre-FM8 needs to test-run and study their entire workflow. Some issue might be managed, but documents needing non-Roman characters can pose economically impractical challenges.

        S
        Community Manager
        Stefan GentzCommunity Manager
        Community Manager
        September 22, 2020

        Exactly so. I see this happening from time to time, and it's nearly always, that the MIFs that were used for translation were created with an outdated plugin used to batch-save all files in a book to MIF. Updating the plugin to support newer versions than FM 7.0 is usually enough to fix the process problem. And as the translations are usually all stored in a Translation Memory, it's usually also enough to just shoot all new MIF files again through the translation process.

        Terms & ConditionsAccessibility statement
        Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices