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

Croatian regional codes.

Bodo Tiegel

I would like to report an issue but I'm not sure if really there is a problem between Trados Studio 2014 and MultiTerm 2014.
I have a project in Trados Studio with the languages combination German-Croatian. This project also has terminology.  When I check the translation, the terminology verifier returns the following error: "Failed to verify document: Sequence contains no matching element".
Well, terminology and project are correct but the terminology is created with the followin regional code "lang =" SH-HR "" while Trados Studio uses as regional code "target-language =" hr-HR "".

There is no way to change this, when the target language is Croatian, MultiTerm always use "SH" (not support HR) but Trados use "HR".

There is a problem with this ??? I can't use the terminology verifier...
Rate translation
×
Suggest better translation
×
Moderator UI
×
  • Get AI Suggestion
Parents
  • 0

    Hi Bodo,

    I didn't test this with 2014 yet, but I did find an interesting problem in 2015 which I'll report to development. The terminology verifier does work for Croatian despite the difference in language codes because they are mapped correctly. However, if I only check the terminology verifier and don't check anything else then the Project Settings refuses to retain the setting. So nothing is verified at all. If I select something else as well then, such as QA Checker then all is well. Once I've closed the Project Setings with other verification checks set, then I can go back and remove the ones I don't want and this time the terminology verifier setting sticks.

    Very odd behaviour. Perhaps you can try that, and in the meantime I'll set up 2014 and test that too.

    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

    Hi Bodo,

    I didn't test this with 2014 yet, but I did find an interesting problem in 2015 which I'll report to development. The terminology verifier does work for Croatian despite the difference in language codes because they are mapped correctly. However, if I only check the terminology verifier and don't check anything else then the Project Settings refuses to retain the setting. So nothing is verified at all. If I select something else as well then, such as QA Checker then all is well. Once I've closed the Project Setings with other verification checks set, then I can go back and remove the ones I don't want and this time the terminology verifier setting sticks.

    Very odd behaviour. Perhaps you can try that, and in the meantime I'll set up 2014 and test that too.

    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