• Replies 5 replies
  • Subscribers 432 subscribers
  • Views 4838 views
  • Users 0 members are here
Options
Related

TIP: How to "fix" the "Check Spelling" for Spanish not working in Studio 2017 and Studio 2015

Former Member
Former Member

Replying to Nora Díaz and for everybody else,

All you have to do is recreate the project, same resources, but with a different Target Language (most of the target segments will be populated automatically). After fiddling with different locales I arrived at the conclusion that for translations into Spanish, simply choose "Spanish (Spain, International Sort)" and don't bother with any other "varieties" of Spanish, and the "Check Spelling" will be there ready for you. However, you also have to change the target language of your Translation Memory. Export your Translation Memory to a TBX file, create a new memory with the new language choices, import that TBX you exported into the new memory and you're all set. Spanish is a very standard language across all countries in terms of spelling, with very, very few exceptions (so, no problem there) unlike American English versus British English.

On the other hand, there seems to be a problem choosing "Spanish (International)" in Studio 2015 and 2017, that I know of. It shows as "ES" (instead of a flag) and "Spanish (International)" in the list of languages. My advice, forget about it. In addition, both Studio versions assign to the translation project a non-standard locale code (es-x-int-SDL) that is non-existent as an ISO code and that could be the problem. Check this page for standard "language culture names" here: https://msdn.microsoft.com/en-us/library/ee825488(v=cs.20).aspx or Google it. For the solution that I propose, SDL Studio assigns, correctly, the language culture name es-ES, the one that does work. As a "bonus", both "Active Spell Checkers" (MS Word and Hunspell) will work (Go to Options / Editor / Spelling). Of course, that will depend on your MS Office settings (in my case I work exclusively in English, but in my "Office Language Preferences" I have Spanish, as well).

 
Rate translation
×
Suggest better translation
×
Moderator UI
×
  • Get AI Suggestion
Parents

  • Thank you for the detailed explanation Ozzie. I thought you meant that you had changed something in the Hunspell files.

    For projects where I have control over the language pairs I always choose ES-MX as the target, as that doesn't give me any issues with spellchecking, but when clients send me files that are already prepared for ES-US or ES-LA, the Hunspell workaround has always worked fine for me and it only takes a couple of minutes to set up after installing or updating Studio. Once that's been done, it will work for every project and file, no need to do anything else. In Studio 2017 the folder is called Studio5, though, not Studio4 as in the original instructions in the thread, so something to consider in case someone wants to give it a try.
  • Former Member
    Former Member in reply to Nora Díaz

    I'm glad this tip could be useful. And, of course, the location of the "Hunspell Dictionaries" will be different for Studio 2017 (C:\Program Files (x86)\SDL\SDL Trados Studio\Studio5) and for Studio 2015 (C:\Program Files (x86)\SDL\SDL Trados Studio\Studio4). Though, for what I explained, you need not bother with changing or renaming files and/or editing XML configuration files. The es-ES is already there, rightfully so, because it's a standard, and, as we know, Spanish is one of the top 5 world languages. In terms of minor differences, there's the decimal separator; es-ES (",") and es-MX ("."), but other than that there aren't really big differences in the "varieties" of Spanish. Colloquial language is another story, of course. Your tip is certainly very helpful and comes in handy for other cases, like the ones you mentioned (could you please post a link?) Cheers!
Reply
  • Former Member
    Former Member in reply to Nora Díaz

    I'm glad this tip could be useful. And, of course, the location of the "Hunspell Dictionaries" will be different for Studio 2017 (C:\Program Files (x86)\SDL\SDL Trados Studio\Studio5) and for Studio 2015 (C:\Program Files (x86)\SDL\SDL Trados Studio\Studio4). Though, for what I explained, you need not bother with changing or renaming files and/or editing XML configuration files. The es-ES is already there, rightfully so, because it's a standard, and, as we know, Spanish is one of the top 5 world languages. In terms of minor differences, there's the decimal separator; es-ES (",") and es-MX ("."), but other than that there aren't really big differences in the "varieties" of Spanish. Colloquial language is another story, of course. Your tip is certainly very helpful and comes in handy for other cases, like the ones you mentioned (could you please post a link?) Cheers!
Children
No Data