• State Suggested Answer
  • Replies 6 replies
  • Answers 2 answers
  • Subscribers 187 subscribers
  • Views 4616 views
  • Users 0 members are here
Options
Related

MultiTerm using outdated/deprecated language code

Sascha Cl

Hi,

MultiTerm 2017 (SR1 - 14.2.6.23639) seems to be still using outdated/deprecated language codes that differ from the ones Trados Studio 2017 uses.

MultiTerm uses:
NO-NO: Norwegian (Bokmal, Norway)
SH-LATN-RS: Serbian (Latin, Serbia)
SH-HR: Croatian (Croatia)

instead of the correct ones Trados Studio uses:

NB-NO: Norwegian (Bokmal, Norway)
HR-HR: Croatian (Croatia)
SR-LATN-RS: Serbian (Latin, Serbia)

This seems to be around and known issue for several years, as can bee seen from some posts:

2013: https://www.proz.com/forum/sdl_trados_support/261535-multiterm_croatian_iso_code_sh_hr_and_not_hr_hr.html

2015: https://community.sdl.com/product-groups/translationproductivity/f/91/t/5720

2017: https://community.sdl.com/product-groups/translationproductivity/f/91/t/13527

I'd like to know when this will finally be fixed?

Thanks and best regards,
Sascha
Rate translation
×
Suggest better translation
×
Moderator UI
×
  • Get AI Suggestion
Parents Reply
  • 0 in reply to Paul Filkin
    Dear Paul,

    When creating MultiTerm TBX files from other software the correct language codes do not work and the files cannot be imported in MultiTerm.
    And creating terminology exports from MultiTerm (e.g. TBX LISA 2002) the outdated language codes are used as well and cannot be imported into other terminology software that expects the correct language codes.
    If you do not want to break backwards compatibility of the deprecated codes at least the correct ones should be accepted as well and the export configurations should allow exporting the correct language codes.

    Best regards,
    Sascha
Children
  • Former Member
    0 Former Member in reply to Sascha Cl

    My two cents. For a quick and dirty solution, open the TBX file with a good text editor (for instance, Notepad++) and replace the attribute "xml:lang" within the langSet tag with the corresponding values. For instance, replace xml:lang="no-NO" with xml:lang="nb-NO", etc. The number of replacements will be equal to the total number of entries. MultiTerm tools, like Glossary Converter, will label the language according to that attribute, e.g. nb-NO = Norwegian Bokmål (endonym: "Norsk Bokmål"). Regards,
  • 0 in reply to Sascha Cl
    Hi

    This is indeed a problem if the other software is not using language codes that are consistent between those that have been mapped for Studio and Multiterm. Your best bet is probably to use the Glossary Converter where you can map the languages at will, and then import. Or merge the termbase and tbx directly in the Glossary Converter, it's a very smart application.

    Paul Filkin | RWS

    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