• State Suggested Answer
  • Replies 5 replies
  • Answers 2 answers
  • Subscribers 433 subscribers
  • Views 1417 views
  • Users 0 members are here
Options
Related

How to fix Studio v2017 spellchecking capability, which has broken down?

Pavel Tsvetkov

Hi All,

For a week now, Studio v2017 has been refusing to spell-check files. The corresponding button is grayed out:

As always, I am translating between English (in this case: en-150) and Bulgarian (and vice-versa), so these are not exotic language choices and all necessary spell-checking modules for Office are installed. 

Interestingly enough, when I export the translated file, which, in this case is in English (en-150), which corresponds to English (Europe), and open it in Word, the latter reports that the language of the file is:

This is not a language I use, and it is not in any way part of the project. Of course, if Trados or Word do indeed communicate that the language of the file is Afar, then Word has not spelling for this language. Also, choosing Hunspell does not help.

Any ideas?

Best regards,

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

    Has this ever worked for you when translating into English (Europe)? I've never tried this before but the Bulgarian to English file I just tested would not spellcheck, even with Hunspell, and the target file for me was Spanish (Latin America) deprecated! I tested to en(UK) and all was well. On this simple test alone I reckon the problem is related to the flavour of English not being properly passed between Studio and Word. I also tested en(India) and the spellcheck didn't work there either although the language code of the word file was also en(India).

    Perhaps your best bet for the time being, and possibly longer as I have no idea whether Word even knows what en-150 is, would be to use Hunspell. Create an additional set of files for Hunspell using this language code:

    gateway.sdl.com/.../communityknowledge

    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
    Hi community.sdl.com/.../pfilkin,

    Thank you for your reply.

    You are right: English (Europe) is the culprit. It seemed like a good idea to use en-150 for EU projects (and moreover now, after Brexit), instead of British English, but... Word cannot spell-check en-150 and on bigger projects it is a chore to spell-check the resulting translation and go back to Studio to implement changes. I tried reading through the instructions about configuring Hunspell, but got lost, frankly.

    I created a new TM (GB-BG), exported the contents of the problematic TM (EU-BG) to .tmx and imported them into the new TM. Then I re-created the AutoSuggest Dictionary, etc.

    On a big TM that takes quite some time, but it is still less than what I initially had in mind: to try to deinstall and reinstall Trados and Multiterm, as I thought that a crash might have ruined the connection between Studio and Word.

    I just wonder why en-150 has been introduced in the first place, though? If it is a non-existent language variant that Word does not recognize?

    Best regards,
    Pavel
  • 0 in reply to Pavel Tsvetkov

    Unknown said:
    I just wonder why en-150 has been introduced in the first place, though? If it is a non-existent language variant that Word does not recognize?

    Good question... I think Hunspell is the only way to resolve this.  It's not that tricky to sort out and I can do this for you if you like?

    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 Children