Hi Antonio Hernandez-Rolon

To find a way of dealing with the issue we would need more clarifications, such as:

Do you have Office installed? Which language pair are you working with?

Do you use the Word spellchecker or have you also tried Hunspell?

Kind regards,

Elisa

Hi, Elisa,

Thank you for your answer.

I have Office installed and I'm working with English (US) - Spanish (International).

I tried both, Hunspell and Word.

I read an old message in which Nora Diaz attached a zip file with some files to be inserted in the Hunspell folder to solve the same problem, but it was for Studio 2006.

Kind regards,

Antonio

If you mean this link:

https://community.sdl.com/product-groups/translationproductivity/f/studio/9513/spell-checker-latin-america-is-disable-language-not-supported

The Hunspell should work with any Trados version.

Please open this path in your Windows Explorer:

C:\Program Files (x86)\SDL\SDL Trados Studio\Studio16\HunspellDictionaries

and drop there the Hunspell dictionary mentioned by Nora.

Thank you very much, Jesús. The problem is that I need the files for International Spanish, and those in the zip file are for Latin American Spanish. Where can I obtain these files?

Thanks in advance,

Antonio

OK, sorry, I got confused…

Have you selected Hunspell dictionary? This will work out-of-the-box. It's my selection too.

If you have selected the MS Word dictionary, then you'd need to have Office installed.

The Hunspell dictionary is selected, but I think the problem is that I do not have the requied files (International Spanish), the files in the zip file that Nora attached are 'es_419' (Latin American Spanish).

That dictionary was posted because the language was a special one and that did the trick. International Spanish Hunspell dictionary is included in Trados Studio.

Could you check if you have got these files (es_ES.aff, es_ES.dic) in this folder?

C:\Program Files (x86)\SDL\SDL Trados Studio\Studio16\HunspellDictionaries

And could you hover the mouse over the Spanish flag at the lower right corner of Trados Studio and let me know the language that pops ups?

Yes, both files are in the folder (es_ES.aff, es_ES.dic) and the language that pops up is Spanish (International).

Your language variant Spanish (International) is not supported by default by Hunspell and is not in the list of Office supported languages. That's the reason it doesn't work, so you shouldn't use it anymore and use Spanish (Modern, for example).

You can anyway take advantage of the Hunspell dictionary. You have a couple of choices:

1. Follow Noras' way: Add a copy of the Spanish AFF and DIC files, rename them somehow and edit the XML accordingly. With this workaround you will need to know your language code.
2. Just add Spanish (Modern) as the second target language to the same project, add a TM with the Modern Spanish variant, populate this TM with the content of the all TM, pre-translate the document and forget about the Spanish variant for good.
3. [If the original format is Word] Create the target file and run the Word spell-checker. If any errors, correct them in Word and also in Studio.

Your language variant Spanish (International) is not supported by default by Hunspell and is not in the list of Office supported languages. That's the reason it doesn't work, so you shouldn't use it anymore and use Spanish (Modern, for example).

You can anyway take advantage of the Hunspell dictionary. You have a couple of choices:

1. Follow Noras' way: Add a copy of the Spanish AFF and DIC files, rename them somehow and edit the XML accordingly. With this workaround you will need to know your language code.
2. Just add Spanish (Modern) as the second target language to the same project, add a TM with the Modern Spanish variant, populate this TM with the content of the all TM, pre-translate the document and forget about the Spanish variant for good.
3. [If the original format is Word] Create the target file and run the Word spell-checker. If any errors, correct them in Word and also in Studio.

Thank you very much, Jesús. Finally, I created a new TM with other variant and now Hunspell works normally.

It is great to have first-hand advice.

Kind regards,

Antonio