Due to essential maintenance, access to Trados cloud will be unavailable on Saturday 30 August from 00:00 to 12:00 UTC.
  • State Suggested Answer
  • Replies 13 replies
  • Answers 4 answers
  • Subscribers 435 subscribers
  • Views 8629 views
  • Users 0 members are here
Options
Related

Language code "sw-CD" not compatible on this system

Matthias Kavuttih

Hi,

Matthias here, a Swahili translator using SDL Trados Studio 2015.

Often, but not always, when opening a Trados Package, I receive the error "language code "sw-CD" not compatible on this system" and the file won't open for translation.

Is this a problem with my app or is it a file format issue?

I will be grateful for your response.

Thank you
Rate translation
×
Suggest better translation
×
Moderator UI
×
  • Get AI Suggestion
Parents
  • 0
    Hi ,

    I had a quick test and see that the language code sw-CD is used in both 2015 and 2017 so this should not be a problem. When it happens again can you open the sdlxliff files in the target language folder of the project package with a text editor and look at the language codes being used? You can open the package by adding a .zip to the end and unzipping it to a folder on your desktop.

    Do you know what version of Studio is used by the creator of the package, or what operating system they use?

    Do you use multiple computers and find this problem happens on only one of them?

    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
    Isn't the message referring rather to the locale (not) being supported by the underlying OS or .NET Framework?
    "sw-CD" locale is not actually supported by any version of Windows, according to msdn.microsoft.com/.../cc233982.aspx
    According to www.microsoft.com/.../default.mspx I would say that Studio should use rather "sw-KE" (which refers to the generic "sw" code) than "sw-CD".
  • 0 in reply to Evzen Polenka
    Quite possibly which is why I asked about the OS. The link you gave for Microsoft is outdated though... try this instead:

    msdn.microsoft.com/.../cc233982.aspx

    W10 introduced Congo Swahili (not the same as Kiswahili) and we will have ensured that this is available in Studio 2017 to support older operating systems too. The code Microsoft use is swc-CD but we seem to have abbreviated it to sw-CD. I don't know any more than that. But certainly I have no problem with this code in W8.1 for Studio 2015 or 2017.

    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
    Actually I gave TWO links, one of them being the one you posted ;-)
    The reason I posted the "outdated" link is that it contains more info about the locales, in particular it shows which "generic" 2-letter languages codes (e.g. "sw" in our case) correspond to region-specific codes (e.g. "sw-KE" in our case) - it's those which differ by 4 in the second digit of the 4-digit LCID hexa code (or which use the same 3-letter language abbreviation): e.g. 0x0009 and 0x0409 for "ENU" English or 0x0041 and 0x0441 for "SWK" Kiswahili.
    In other words, it helps one to get the correct region-specific code if all one gets is the generic language name (e.g. to know which of the "Catalan" languages available in Studio is "the right one" when client just says "Catalan").
    That's something you won't see in other tables on other links... and that's the reason why this table is still VERY valuable.

    Now, since the weird "sw-CD" code for "Swahili (Congo - Kinshasa)" language is used since at least Studio 2011 (and most probably also in Studio 2009, but I don't have it installed), it really strongly doubt that it has anything to do with "abbreviation of swc-CD".
    It seems to be rather related to some "home-brewed" code back in the times of missing codes for "Latin American Spanish" and the likes...
Reply
  • 0 in reply to Paul
    Actually I gave TWO links, one of them being the one you posted ;-)
    The reason I posted the "outdated" link is that it contains more info about the locales, in particular it shows which "generic" 2-letter languages codes (e.g. "sw" in our case) correspond to region-specific codes (e.g. "sw-KE" in our case) - it's those which differ by 4 in the second digit of the 4-digit LCID hexa code (or which use the same 3-letter language abbreviation): e.g. 0x0009 and 0x0409 for "ENU" English or 0x0041 and 0x0441 for "SWK" Kiswahili.
    In other words, it helps one to get the correct region-specific code if all one gets is the generic language name (e.g. to know which of the "Catalan" languages available in Studio is "the right one" when client just says "Catalan").
    That's something you won't see in other tables on other links... and that's the reason why this table is still VERY valuable.

    Now, since the weird "sw-CD" code for "Swahili (Congo - Kinshasa)" language is used since at least Studio 2011 (and most probably also in Studio 2009, but I don't have it installed), it really strongly doubt that it has anything to do with "abbreviation of swc-CD".
    It seems to be rather related to some "home-brewed" code back in the times of missing codes for "Latin American Spanish" and the likes...
Children
  • 0 in reply to Evzen Polenka

    Unknown said:
    Actually I gave TWO links, one of them being the one you posted ;-)

    So you did... sorry.  That one does indeed provide more information but it's only valid up to W7 and as you clearly know there has been a lot more languages added since that version.

    Unknown said:
    Now, since the weird "sw-CD" code for "Swahili (Congo - Kinshasa)" language is used since at least Studio 2011 (and most probably also in Studio 2009, but I don't have it installed), it really strongly doubt that it has anything to do with "abbreviation of swc-CD".
    It seems to be rather related to some "home-brewed" code back in the times of missing codes for "Latin American Spanish" and the likes...

    I'm only guessing, but I will ask the question since it seems to have attracted this much attention from you.  I'm sticking with my guess though as 2011 used that code for "Swahili (Congo - Kinshasa)" as you pointed out, probably because it was missing from the Microsoft language support, and now that we had a need for more African languages from the Democratic Republic of Congo (country code CD) we stuck with the abbreviation we used then for Swahili (sw) and added support for the others (French, Lingala, Luba-Catanga) that all have two digit language codes.  So Swahili was the only one that was different in that they used swc - so probably we were unlucky with the guess.

    Apologies to the OP too... hopefully he'll still come back to discuss his original problem!

    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
    Yes, I would also guess this is what happened.
    Another sign of 'non-standardness' is the dash used in the "Swahili (Congo - Kinshasa)" name, plus the usage of city name, which is also unusual in standard language names coming from the system (e.g. by using GetLocaleInfoEx API call)