• State Suggested Answer
  • Replies 11 replies
  • Answers 2 answers
  • Subscribers 432 subscribers
  • Views 5048 views
  • Users 0 members are here
Options
Related

Issues with languages codes; Windows 10 - Studio 2014

Daniela Badel

Several of our translation memories (source language English - United Kingdom) cannot be used with Studio 2014 and Windows 10.

When exporting tmx from the TM we recognised that there are differences whether the tmx is exported from Win10 or Win7 resp. XP.

The language code in the tmx file of Windows 10 indicated en-UK instead of en-GB.

The question is, why does the export of the same TM show different language codes on Win10 and Win7 rsp. WinXP?

We already found a solution in order to use the tm content nevertheless: When importing the modified tmx file (with the correct ‘Studio language’ code en-GB) into a new Studio TM, we can use it without issues.

But this is a very time-consuming solution.

Do you have any other suggestions? Why does this problem occur in the first place? 

Thank you very much!
Rate translation
×
Suggest better translation
×
Moderator UI
×
  • Get AI Suggestion
Parents
  • 0

    Hi Daniela,

    The problem may be occuring because Studio draws it's language codes from the operating system.  There are quite some differences between W7 and W10.

    However, I wasn't aware that these differences would give you a problem like this. I just ran a test and imported an en(GB) and an en(UK) TMX file into an en(US) file.  So these kind of variances should not cause a problem.

    I didn't use W10 though, I only have W8.1.  But I tested on 2014 and 2015 and both managed this without a complaint.  Can we see the header from your TMX files that are failing, and maybe one or two TUs?

    Regards

    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

  • 0 in reply to Paul

    Hi Paul,

    here are two screenshots. Thanks you very much for your support.

    Best regards,

    Daniela
  • 0 in reply to Daniela Badel
    Could you just attach the file instead of the screenshot... then I can test it without having to retype it?

    Regards

    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

  • 0 in reply to Paul
    Would copy&paste of the header do? I am not allowed to send the whole tmx-file...
  • 0 in reply to Daniela Badel
    Yes... I can make up the rest :-) Although it would be good to have a few segments if you have custom attributes. Perhaps you can anonymise the text for a few segments too?

    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

    WIN 10 TMX

    <?xml version="1.0" encoding="utf-8"?>
    <tmx version="1.4">
    <header creationtool="SDL Language Platform" creationtoolversion="8.0" o-tmf="SDL TM8 Format" datatype="xml" segtype="sentence" adminlang="en-UK" srclang="en-UK" creationdate="20150106T162813Z" creationid="ENTERPRISE\bad">
    <prop type="x-Recognizers">RecognizeDates, RecognizeTimes, RecognizeNumbers, RecognizeAcronyms, RecognizeVariables, RecognizeMeasurements</prop>
    <prop type="x-TMName">NDB_SDL2011_en-GB_et-EE</prop>
    </header>
    <body>
    <tu creationdate="20150106T165819Z" creationid="ENTERPRISE\wea" changedate="20150106T165819Z" changeid="ENTERPRISE\wea" lastusagedate="20150112T142331Z">
    <prop type="x-Context">0, 0</prop>
    <prop type="x-Context">124, 124</prop>
    <prop type="x-Context">3364556739114585, 3364556739114585</prop>
    <prop type="x-Origin">TM</prop>
    <prop type="x-ConfirmationLevel">Translated</prop>
    <tuv xml:lang="en-UK">
    <seg>„<ph x="1" type="0" />“ auf Seite <ph x="2" type="1" /></seg>
    </tuv>
    <tuv xml:lang="et-EE">
    <seg>„<ph x="1" type="0" />“ auf Seite <ph x="2" type="1" /></seg>
    </tuv>
    </tu>
    <tu creationdate="20150106T165819Z" creationid="ENTERPRISE\wea" changedate="20150106T165819Z" changeid="ENTERPRISE\wea" lastusagedate="20150114T150532Z">
    <prop type="x-Context">3513344214695, 3801313</prop>
    <prop type="x-Context">3364556739114585, 3364556739114585</prop>
    <prop type="x-Origin">TM</prop>
    <prop type="x-ConfirmationLevel">Translated</prop>
    <tuv xml:lang="en-UK">
    <seg>„<ph x="1" type="2" />“</seg>
    </tuv>
    <tuv xml:lang="et-EE">
    <seg>„<ph x="1" type="2" />“</seg>
    </tuv>
    </tu>
    <tu creationdate="20150106T165819Z" creationid="ENTERPRISE\wea" changedate="20150106T165819Z" changeid="ENTERPRISE\wea" lastusagedate="20150106T165819Z">
    <prop type="x-Context">124, 124</prop>
    <prop type="x-Origin">TM</prop>
    <prop type="x-ConfirmationLevel">Translated</prop>
    <tuv xml:lang="en-UK">
    <seg><ph x="1" type="6" /> auf Seite <ph x="2" type="7" /></seg>
    </tuv>
    <tuv xml:lang="et-EE">
    <seg><ph x="1" type="6" /> auf Seite <ph x="2" type="7" /></seg>
    </tuv>
    </tu>
    <tu creationdate="20150106T165819Z" creationid="ENTERPRISE\wea" changedate="20150106T165819Z" changeid="ENTERPRISE\wea" lastusagedate="20150106T165819Z">
    <prop type="x-Context">124, 124</prop>
    <prop type="x-Origin">TM</prop>
    <prop type="x-ConfirmationLevel">Translated</prop>
    <tuv xml:lang="en-UK">
    <seg>Seite <ph x="1" type="12" /></seg>
    </tuv>
    <tuv xml:lang="et-EE">
    <seg>Seite <ph x="1" type="12" /></seg>
    </tuv>
    </tu>
    <tu creationdate="20150106T165819Z" creationid="ENTERPRISE\wea" changedate="20150106T165819Z" changeid="ENTERPRISE\wea" lastusagedate="20150106T165819Z">
    <prop type="x-Context">3659333155, 3659333155</prop>
    <prop type="x-Origin">TM</prop>
    <prop type="x-ConfirmationLevel">Translated</prop>
    <tuv xml:lang="en-UK">
    <seg>DROP</seg>
    </tuv>
    <tuv xml:lang="et-EE">
    <seg>DROP</seg>
    </tuv>
    </tu>
    <tu creationdate="20150106T165819Z" creationid="ENTERPRISE\wea" changedate="20150106T165819Z" changeid="ENTERPRISE\wea" lastusagedate="20150114T150532Z">
    <prop type="x-Context">3645873265, 3645873265</prop>
    <prop type="x-Context">3517044651680, 3517044651680</prop>
    <prop type="x-Origin">TM</prop>
    <prop type="x-ConfirmationLevel">Translated</prop>
    <tuv xml:lang="en-UK">
    <seg>USER MANUAL</seg>
    </tuv>
    <tuv xml:lang="et-EE">
    <seg>KASUTUSJUHEND</seg>
    </tuv>
    </tu>

    WIN XP TMX

    <?xml version="1.0" encoding="utf-8"?>
    <tmx version="1.4">
    <header creationtool="SDL Language Platform" creationtoolversion="8.0" o-tmf="SDL TM8 Format" datatype="xml" segtype="sentence" adminlang="en-GB" srclang="en-GB" creationdate="20150106T162813Z" creationid="ENTERPRISE\bad">
    <prop type="x-Recognizers">RecognizeAll</prop>
    <prop type="x-TMName">NDB_SDL2011_en-GB_et-EE</prop>
    </header>
    <body>
    <tu creationdate="20150106T165819Z" creationid="ENTERPRISE\wea" changedate="20150106T165819Z" changeid="ENTERPRISE\wea" lastusagedate="20150112T142331Z">
    <prop type="x-Context">0, 0</prop>
    <prop type="x-Context">124, 124</prop>
    <prop type="x-Context">3364556739114585, 3364556739114585</prop>
    <prop type="x-Origin">TM</prop>
    <prop type="x-ConfirmationLevel">Translated</prop>
    <tuv xml:lang="en-GB">
    <seg>„<ph x="1" type="0" />“ auf Seite <ph x="2" type="1" /></seg>
    </tuv>
    <tuv xml:lang="et-EE">
    <seg>„<ph x="1" type="0" />“ auf Seite <ph x="2" type="1" /></seg>
    </tuv>
    </tu>
    <tu creationdate="20150106T165819Z" creationid="ENTERPRISE\wea" changedate="20150106T165819Z" changeid="ENTERPRISE\wea" lastusagedate="20150114T150532Z">
    <prop type="x-Context">3513344214695, 3801313</prop>
    <prop type="x-Context">3364556739114585, 3364556739114585</prop>
    <prop type="x-Origin">TM</prop>
    <prop type="x-ConfirmationLevel">Translated</prop>
    <tuv xml:lang="en-GB">
    <seg>„<ph x="1" type="2" />“</seg>
    </tuv>
    <tuv xml:lang="et-EE">
    <seg>„<ph x="1" type="2" />“</seg>
    </tuv>
    </tu>
    <tu creationdate="20150106T165819Z" creationid="ENTERPRISE\wea" changedate="20150106T165819Z" changeid="ENTERPRISE\wea" lastusagedate="20150106T165819Z">
    <prop type="x-Context">124, 124</prop>
    <prop type="x-Origin">TM</prop>
    <prop type="x-ConfirmationLevel">Translated</prop>
    <tuv xml:lang="en-GB">
    <seg><ph x="1" type="6" /> auf Seite <ph x="2" type="7" /></seg>
    </tuv>
    <tuv xml:lang="et-EE">
    <seg><ph x="1" type="6" /> auf Seite <ph x="2" type="7" /></seg>
    </tuv>
    </tu>
    <tu creationdate="20150106T165819Z" creationid="ENTERPRISE\wea" changedate="20150106T165819Z" changeid="ENTERPRISE\wea" lastusagedate="20150106T165819Z">
    <prop type="x-Context">124, 124</prop>
    <prop type="x-Origin">TM</prop>
    <prop type="x-ConfirmationLevel">Translated</prop>
    <tuv xml:lang="en-GB">
    <seg>Seite <ph x="1" type="12" /></seg>
    </tuv>
    <tuv xml:lang="et-EE">
    <seg>Seite <ph x="1" type="12" /></seg>
    </tuv>
    </tu>
    <tu creationdate="20150106T165819Z" creationid="ENTERPRISE\wea" changedate="20150106T165819Z" changeid="ENTERPRISE\wea" lastusagedate="20150106T165819Z">
    <prop type="x-Context">3659333155, 3659333155</prop>
    <prop type="x-Origin">TM</prop>
    <prop type="x-ConfirmationLevel">Translated</prop>
    <tuv xml:lang="en-GB">
    <seg>DROP</seg>
    </tuv>
    <tuv xml:lang="et-EE">
    <seg>DROP</seg>
    </tuv>
    </tu>
    <tu creationdate="20150106T165819Z" creationid="ENTERPRISE\wea" changedate="20150106T165819Z" changeid="ENTERPRISE\wea" lastusagedate="20150114T150532Z">
    <prop type="x-Context">3645873265, 3645873265</prop>
    <prop type="x-Context">3517044651680, 3517044651680</prop>
    <prop type="x-Origin">TM</prop>
    <prop type="x-ConfirmationLevel">Translated</prop>
    <tuv xml:lang="en-GB">
    <seg>USER MANUAL</seg>
    </tuv>
    <tuv xml:lang="et-EE">
    <seg>KASUTUSJUHEND</seg>
    </tuv>
    </tu>
  • 0 in reply to Daniela Badel
    Hi Daniela,

    I created two TMX files from your examples (thank you, this was helpful). I then created two SDLTM files, one copied from the other so they are exactly the same and empty. I then imported one TMX files into them. Both worked perfectly and didn't complain, despite the language codes being used.

    Now, that was using Studio 2015.

    I then tested again using Studio 2014 and created a new empty SDLTM in 2014 just in case... this also worked seamlessly.

    Can you tell me what the issues are that you experience here? I think we're going to need more information as I have no problems with these TMs at all.

    Regards

    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
  • 0 in reply to Daniela Badel
    Hi Daniela,

    I created two TMX files from your examples (thank you, this was helpful). I then created two SDLTM files, one copied from the other so they are exactly the same and empty. I then imported one TMX files into them. Both worked perfectly and didn't complain, despite the language codes being used.

    Now, that was using Studio 2015.

    I then tested again using Studio 2014 and created a new empty SDLTM in 2014 just in case... this also worked seamlessly.

    Can you tell me what the issues are that you experience here? I think we're going to need more information as I have no problems with these TMs at all.

    Regards

    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

Children