• State Suggested Answer
  • Replies 3 replies
  • Answers 2 answers
  • Subscribers 431 subscribers
  • Views 1550 views
  • Users 0 members are here
Options
Related

URGENT - Target *.mif files show empty in MemoQ

Paola

My client sent me 33 *.mif files, as they work with MemoQ but I'd rather work in Studio. I am translating from English (United States) to Italian (Italy).

I was able to import them in Studio, translate them and generate target *.mif files. However, my client says that the target column is shown empty in MemoQ.

In fact, the 33 source *.mif files were about 370 MB, and my 33 target *.mif files are 370MB as well. Their icons in MacOs are displayed differently (black the source, white the target). It looks like something is not working in the generation of the target files.

 

I have already worked with this client in this manner (mif to sdlxliff to mif) and had no issues back then. Please help as today is the deadline!
Rate translation
×
Suggest better translation
×
Moderator UI
×
  • Get AI Suggestion
Parents
  • 0
    Hi Paola (PaolaSlajmer) ,

    If I get this right it sounds as though this is your process:

    1. You create a project in Studio with MIF files
    2. You create target MIF files and send them to your client
    3. Your client opens the MIF files in memoQ and can't see a translation

    If this is correct then I wonder you'd expect as MIF files are monolingual?

    I don't understand what you are showing in the screenshot, it just looks like a list of files. I'm sure I'm missing something from your explanation.

    Paul Filkin | RWS Group

    ________________________
    Design your own training!
    You've done the courses and still need to go a little further, or still not clear? 
    Tell us what you need in our Community Solutions Hub

  • 0 in reply to Paul

     , thank you for your prompt answer. It looks like there was a misunderstanding between the PMs. The *.mif files should be fine (and monolingual, as you said), but they wanted to see them translated in MemoQ as due to different segmentation, Studio handles *.mif files differently than MemoQ and thus they are afraid to 'lose some translation' this way. 

    I was then asked to check the project in MemoQ (applying the *.tmx from Studio and fixing the differences due to segmentation). Maybe we should delete this thread entirely, as it is a non-issue.

    Thank you so much for your time!

     

     

    I just have one question left: why if I load the target *.mif in Memoq, I am seeing them in English only, instead of Italian only?
Reply
  • 0 in reply to Paul

     , thank you for your prompt answer. It looks like there was a misunderstanding between the PMs. The *.mif files should be fine (and monolingual, as you said), but they wanted to see them translated in MemoQ as due to different segmentation, Studio handles *.mif files differently than MemoQ and thus they are afraid to 'lose some translation' this way. 

    I was then asked to check the project in MemoQ (applying the *.tmx from Studio and fixing the differences due to segmentation). Maybe we should delete this thread entirely, as it is a non-issue.

    Thank you so much for your time!

     

     

    I just have one question left: why if I load the target *.mif in Memoq, I am seeing them in English only, instead of Italian only?
Children