• State Verified Answer
  • Replies 6 replies
  • Answers 2 answers
  • Subscribers 188 subscribers
  • Views 2726 views
  • Users 0 members are here
Options
Related

Appropriate locale output in Multiterm Convert

Paulo Sousa

I am trying to convert a IATE TBX export (a subset) into a Multiterm 2017 termbase.

The TBX file is about 13 MB in size and the export contains EN and PT as locales. The Java applet that created the export does not have an option to turn those two top locales into what it is more appropriate gb-EN and pt-PT.

Multiterm Convert seems to handle the conversion process flawlessly but the resulting files have got the wrong locales: they're set to US English and Brazilian Portuguese.

Any ideas on how to fix this are much appreciated.
Rate translation
×
Suggest better translation
×
Moderator UI
×
  • Get AI Suggestion
Parents
  • 0
    Hi Paulo,

    The locale is set by the TBX, so if you want to use MultiTerm Convert and not the Glossary Converter which is much easier (not sure why you don't use this) then just change the language codes in the TBX before the conversion.

    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

    Hello, Paul.

    Thank you for getting back to me.

    I don't think the culprit is the TBX file (that was my initial impression as well but the IATE people confirmed that it was not the case): the TBX file has got the following locale variables: <langSet xml:lang="en"> and <langSet xml:lang="pt">. There is no reference in it to either the USA or to Brazil.

    The XTD file created by Multiterm does reference both locales explicitly.

    I did try to use Glossary Converter before logging my question and the tool creates a us-EN->p-PT term base, which is closer to the facts but still not 100% accurate. I have no problem in using the Glossary Converter, but the tool is not (correct me if I'm wrong!) officially supported by SDL and I would have to rely on the generosity of the developer for help.

    I haven't been able to find anything on the Internet or the Help files that explains why this is happening (is this caused by the TBX not mentioning explicitly that it's gb-EN, etc.?) and, more importantly, how to fix it.

    Cheers

    Paulo
  • 0 in reply to Paulo Sousa
    Hi Paulo,

    I'm a little confused by your response as you seem to be agreeing with me on the problem... but you say it's not. Try changing the codes to:

    <langSet xml:lang="EN-GB"> and <langSet xml:lang="PT-PT">

    That would do it I think.

    On the Glossary Converter... you are correct in that SDL do not support this tool, but you should not let this put you off. This tool is far more capable and easy to use than MultiTerm Convert, it handles things that still cause bugs in MultiTerm Convert and the developer is incredibly knowledgeable and helpful. The appstore is an SDL feature and we do test every app that is approved for use on the store even if we don't support those developed by others ourselves.

    However, it is of course your choice and if you prefer to go through the steps required to achieve this in MultiTerm Convert then this is obviously your decision. The end result will be the same... I would just prefer to make it easy on myself :-) This app is not the most downloaded and used app on the store for nothing!

    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

    Thank you for your quick reply, Paul!

    That worked for Glossary Converter (both locales are now properly set) but, alas!, not for Multiterm:

     

     

    This seems like a genuine bug in the tool. I did try to manually edit the XTD file before logging the initial question as well, but got nowhere with the itemlocale variables in it (I'm guessing this is also related to the standard Microsoft schemas mentioned in the file, but who knows? :) ).

    In any case, I've got a fully working term base now, so I'm putting the case to rest! :)

    Cheers

    Paulo
Reply Children