Hi Vicente,

In that case, I think I can help. I use a workaround for this that involves using the Hunspell spellchecker. You need to do the following:

1. Place the attached files in C:\Program Files (x86)\SDL\SDL Trados Studio\Studio4\HunspellDictionaries. The xml should replace the one already present in the folder.

2. Go to Options-Editor-Spelling-Active Spell Checker and select Hunspell instead of Word.

Please note that this needs to be done again if you ever repair Studio or install a new version which replaces the modified xml.

Hope that helps!

Nora

Hunspell_workaround files_ES.zip

Hi, Nora. This solution does work for Studio 2017 SR1, provided that you change from Spanish International to any other Spanish variety. I've tried this, following carefully these instructions (yours and Paul Filkin's somewhere else) and the dreaded disabled "Check Spelling" kept showing.

Then, I changed from Spanish International (not sure about the ISO code and that is the locale that doesn't seem to work) to es-MX and then, voilà!, the spell checker works. Now, even the Microsoft Spell checker is also working!

However, I would think this problem should've been fixed by now (Studio 2017 SR1).

Thanks!

Nora,

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. 

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" (ISO 639x Values) 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-EX, the one that does work.