importing a memoQ *.mqxlz file into Studio 2019 when just plain 'English' is the target language

When a client sends me a MemoQ *.mqxlz file where the target language is English (that is, not English - United Kingdom, which are the only options in MemoQ), Studio 2019 won't import the file as there is no target language that matches just 'English' in Studio.

I can create a project in MemoQ using the target language that Studio will accept (that is English - United Kingdom) and add the file that I got from the client, then export it as a bilingual file (*.mqxlz but now with the target language English - United Kingdom) and create a project in Studio with this file, translate it, then Finalize. Then I can import the file back into MemoQ and it is all fine.

But then when I export the translated file from MemoQ and send it to the client, the client can't import it because the target languages don't match.

Is there any way around this problem? I don't like using MemoQ as I am much more familiar with Studio, but in such cases I am forced to at present.

Best

Katherine

Parents
  •  

    Unknown said:
    When a client sends me a MemoQ *.mqxlz file where the target language is English (that is, not English - United Kingdom, which are the only options in MemoQ),

    This is not correct:

    MemoQ language selection dropdown menu showing English with various country options but lacking a plain English option.

    Having said this even if just English is selected Studio will handle this without a problem.  I just created a project in memoQ using just English and just Romanian.  When I open in Studio it opens as en(US) - ro(RO). It will do this for single file projects and for standard Studio projects.

    The difference between these two methods is this:

    Single file project

    You can change the languages when you open the file by selecting whatever language you like  and Studio will give you a message saying the language codes don't match.  But you can ignore this and just work with the file.  The resultant export of the target file will import succuessfully into the original memoQ project and updated the project files.

    Standard Studio Project

    You can change the languages here too.  But the difference is that Studio will complain when the project is created and you won't be able to work on it.  So when working with a standard project workflow you need to work with the en(US) and ro(RO) (in my example) that was suggested and then all is well.  I tested this roundtriup and well as the single file approach and it also updates the memoQ project without any problems.

    Unknown said:
    Is there any way around this problem? I don't like using MemoQ as I am much more familiar with Studio, but in such cases I am forced to at present.

    You mentioned that Studio won't import the file?  Can you elaborate on how you are working?  Are you perhaps adding files to an ever growing project?  Or are you creating new projects for your jobs?  It might help to reproduce your problem if we know what you are doing.

    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

    emoji


    Generated Image Alt-Text
    [edited by: Trados AI at 3:45 PM (GMT 0) on 28 Feb 2024]
  • Hi Paul,

    When I add the mqxlz file (which has just "English" as the target language, which I can't change since otherwise the translated file will not import back into my client's TM) in Studio 2019 to a new 'clean' project, Studio will load the file and mark it as Translatable. But I can't actually open the file to start translating it. I get the error message "The detected target language does not match that expected by the project." and nothing - the file doesn't open so I can't work on it.

    I haven't tried the Standard Studio project approach you suggest, as I'm not sure exactly what to do - I would need more detailed instructions.

    However I followed your suggestion for a single file and that did work! Thanks!! I also tested the roundtrip and it opened fine in MemoQ with just English as the target language.

    Best regards and many many thanks!
    Katherine
  • Unknown said:
    I haven't tried the Standard Studio project approach you suggest, as I'm not sure exactly what to do - I would need more detailed instructions.

    Hi  

    It sounds as though you are using the Standard Project as the error you describe sounds like the one I mentioned above.  Glad the single file translation worked for you though.

    Paul

    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

Reply Children
No Data