Hi Sandor Juhasz 

Running a Windows Repair of Studio 2019 should create a clean version that prompts you to enter your 5 languages again. Maybe rebooting your system before opening Studio again might help.

If that doesn't work then reinstalling is the answer. There is no other way I'm afraid.

All the best,

Alison

Hi Christian Schmidt 

As indicated in my first post in this thread, running a Windows Repair of SDL Trados Studio should be enough to reset Studio so that next time you open Studio you will be prompted to add 5 languages again.

If that doesn't work (which until now has been rare) then reinstalling Studio normally resets Studio so that you have to add 5 languages again.

All the best,

Alison

Hi Sandor Juhasz

Thank you, that's useful to know. I'll make a note of that for future searchers.

I'm so glad they were able to resolve your issue so simply!

All the best,

Ali :)

PS: 

Hi Paul 

Do you think that in future we can tell folk who haven't been able to change their 5 languages via reinstallation or repair, that they can use the method given to Sandor by the Help Team?

In other words, by editing the registry (HKEY_CURRENT_USER\Software\Microsoft\LDSRClient15 was renamed to LDSRClient15.old)

Or should we not be advising folk to amend their registry...? Maybe that's a step too far into reset territory?

Ali

Hi!

I followed these instructions carefully with some online explanations and it all worked well! (Never thought about being able to edit the registry). Thanks a lot!

Rosaria

Hi Rosaria Rizza

You're welcome! I'm very glad to hear that this worked for you!

All the best

Ali :)

Hi Neil Allen 

Studio's user-friendliness depends on your perspective. At the other end of the spectrum, I recall a user complaining because he couldn't add a 6th language. As it turns out, he had added 2 variants of one language, UK and US English and you only need one of them to be able to use all other variants. Thus he added just UK English, which gave him another language allowed.

I know what you mean, though. It would be easier if Studio Freelance could be set up with just the two or three languages one user needs. However, as normally the entry of the languages only happens on installation, reset or reinstallation and it only takes a second or two more to select another language, it's not that much of an inconvenience in my book. I've actually found it useful as I can run a quick machine translation on something in a different language that I don't normally use, just to get an idea of what it means.

Anyway, I hope you enjoy using Studio and MultiTerm as much as I do, and have for many years!

All the best,

Ali :)

The point here is something else... something what was already discussed few years ago, but still wasn't fixed, apparently.

Back in Trados, this dialog in question asked to select up to five languages... while in Studio you have to select precisely five languages.
Feel the (user unfriendly) difference?

Adding more to the issue, the fact that only the "main" languages are significant (i.e. English-US means automatically all other flavors of English) is not taken in account in the "precisely five languages" requirement.

The point here is something else... something what was already discussed few years ago, but still wasn't fixed, apparently.

Back in Trados, this dialog in question asked to select up to five languages... while in Studio you have to select precisely five languages.
Feel the (user unfriendly) difference?

Adding more to the issue, the fact that only the "main" languages are significant (i.e. English-US means automatically all other flavors of English) is not taken in account in the "precisely five languages" requirement.

Unknown said:

Also, logically, one would expect the languages to depend on the project, not the original installation.

The original, decades-old, idea behind the number five was that up to five languages should be enough for majority of common freelance translators, i.e. excluding multilingual superheroes. Plus, since the idea is decades-old, the number of supported languages at that time was way lower... definitely there weren't dozens of flavors of the same main language.

So, the Trados Freelance allowed to select up to five languages which the translator expected to use in the variety of his/her projects... which did make sense and worked quite well at that time.

Unknown said:

Adding more to the issue, the fact that only the "main" languages are significant (i.e. English-US means automatically all other flavors of English) is not taken in account in the "precisely five languages" requirement.

Unknown said:

I don't know why Studio is set like that but it has been so ever since Studio 2019 was first created. Maybe the programmers found it easier to do everything in 5's throughout the program for some reason.

It's a clear bug. Because it's totally illogical. And it was different (and most importantly LOGICAL) back in Trados.

Making something "easier fior programmers" would be ridiculous reason, especially if it means obstacles and discomfort for users.
Nr. 1 rule in programming is that USERS set the rules, not programmers. The world is not here to make life easier for programmer, but for the USER!

I can't tell right away what should be the UX, because I don't know the precise SDL's rules.
It's SDL's job to make their "what exactly is considered 'one language' in 'maximum number of languages' available in Freelance edition" rule to play correctly with the dialog.

What they should start with ASAP for sure is to fix the incorrect "precisely five" condition back to "up to five".
This is a clear bug and I can imagine how it was born - simply by information noise or programmer's misunderstanding of the specification when SDL took over Trados.

Here is a screenshot in older thread: community.sdl.com/.../46275