"Probability score": 0.6

"Question improvement suggestion": Please provide more details such as the version of Trados Studio you are using, the specific language code combinations you are trying to map, and any error messages you might be seeing. Also, let us know if there have been any recent changes to your system or software.

In the meantime, based on the information you have provided, here is a suggested answer to your question:

Hello,

I understand that you're having trouble with the Language Mapping feature in Trados Studio and that the Apply button is not becoming active. This could be due to a number of reasons. Here are a few steps you can try:

Step 1: Ensure that you have the latest updates for Trados Studio. You can check for updates within the application.

Step 2: Try resetting your settings in Trados Studio. You can do this by going to File > Setup > Reset to Default Settings. Please note that this will reset all your settings, so you may want to back them up first.

Step 3: If the issue persists, you may want to try reinstalling Trados Studio. Please make sure to back up any important data before doing so.

Regarding the outdated wiki articles, we appreciate your feedback. The team responsible for maintaining these articles has been notified and will update them as soon as possible.

I hope this answer addressed your question. If not, please reject the answer, add the question improvement suggestion information, and click the RWS Community AI checkbox on the right to try again.

RWS Community AI

Sorry; this reply is far to general and vague. I can tell that none of the suggested remedies will work.

It did help! But in fact, I knew almost all of this before, and had written about it. The problem in this case is that my old example, in my old text, was to use German for translation into Luxembourgish -- however, since that "combination" is now already listed in the mappings table, it was in fact unnecessary to make this manipulation, and the existence of the combination is obviously the reason why the Apply button never lit up. I did not realise that (it is a long time since my old text).

- But now that I try this again, it seems it is not enough that the language code ger (for Luxembourgish) is already listed -- if I don't click Apply, it will not be used by LW! So what could be the reason for the Apply button being inactive?

However, another question: To try a better combination, I picked Igbo, to be translated using the language code for Nigerian. But there is no language code for that! And I suppose the answer is that the language codes list only contains some of the ones "missing" in the Language Weaver list -- you just have to be lucky!

Just one more question: Above the list in LW Provider, it says (in a certain case) "Total languages 599, Filtered 155". How are the "total" languages defined?

(My apologies to the AI assistand; the original question was directed to a human and I did not think to rephrase it for AI use. Still, I doubt I could have a much better reply than the original one even with a suitable rephrasing.)

Anyway, the wiki texts still need updating.

Mats Linder 

Mats Linder said:

To try a better combination, I picked Igbo, to be translated using the language code for Nigerian. But there is no language code for that! And I suppose the answer is that the language codes list only contains some of the ones "missing" in the Language Weaver list -- you just have to be lucky!

Not exactly.  If Language Weaver doesn't support Nigerian (which I don't believe it does) then how could it work?  It would be very cool if you could select any language you like and Language Weaver just did it :-)

Mats Linder said:

Above the list in LW Provider, it says (in a certain case) "Total languages 599, Filtered 155". How are the "total" languages defined?

They are all the languages supported in Trados Studio.  600 in my instance:

Mats Linder said:

I doubt I could have a much better reply than the original one even with a suitable rephrasing.

Maybe... maybe not, but we'll never know.  You will however if you try again as I just added some training material for this feature :-)

Paul said:

You will however if you try again as I just added some training material for this feature :-)

You mean ask the AI again? Maybe I will, just to see what happens. But meanwhile, you did not answer my question about why the Apply button refuses to light up so that I can apply the selected language mapping. (I assume that my first assumption, that I needed to add a missing language code cannot be right -- surely I should be able to use any suitable language code in the mapping table.)

Mats Linder 

Mats Linder said:

You mean ask the AI again?

No, I just said IF you try again.  It wasn't a request, I just meant it's improved because I added training material to handle this and I already know that even if I ask a question like yours, which didn't mention LW at all, that Trados doesn't have this feature so it must be LW and I added some explanatory Q&A into the training data so even the response to your original question is adequate.

Mats Linder said:

you did not answer my question about why the Apply button refuses to light up so that I can apply the selected language mapping. (I assume that my first assumption, that I needed to add a missing language code cannot be right -- surely I should be able to use any suitable language code in the mapping table.)

It's hard to know Mats... if it happens again let me know.  The main thing is that this relates to mapping available languages from LW so they can be used anywhere you see fit.  So "suitable" means it must be available in the LW supported language list.

Sorry for this lengthy reply…

In your example, ”Language” is the actual target language, and “Region” is the language for the MT service. However, in my  example in my old text (which I am now trying to update)

at tradosstudiomanual.com/

and, it seems, in most language pairs in the mapping list, it is the other way around (which worked when I wrote that text).

Also in your example, the Trados code for your selection is tt-RU (with the code “rus”), while for instance in the numerous Arabic pairs in the list, it is the other way around: The code “ara” stands for e.g. the *Language* arabic together with a specific Region, so that the Trados code is, e.g., ar-IQ.

My question then is: What is really the target language and what is the MT lanugage? (Too bad the old wiki entries are now deleted; I am sure that I would have found some answers there.)

I can add that I can activate the Apply button by entering a letter – any letter – in a empty Language code field. And then I can select any pair, e.g., Germany-Luxembourg, with the Apply button still active. BUT when I click it, I get this error message:

and the LW dialog is closed; I am back at the selection of TM/AT.

Strange, isn’t it?

Paul said:

I added training material

Where is it?

Mats Linder 

Decided to record for the response:

Wow! Thanks a lot! Your reply, and my guesses, shows that a little knowledge can be a dangerous thing.

But unfortunately, I'm still stuck with the original problem, trying to map Luxembourgish on German:

I.e. the Apply button is not active. Any suggestion?

BTW, I think the old way of showing the target was very elegant. A pity it is not used any longer.

PS. I'm pretty sure the old wiki text on the language mapping was more exhaustive than the one you refer to. But of course I can't be sure.

Mats Linder 

Mats Linder said:

BTW, I think the old way of showing the target was very elegant. A pity it is not used any longer.

Completely different feature!  That also didn't provide any mapping capability to use a completely different language to the ones in your project.

Mats Linder said:

I.e. the Apply button is not active. Any suggestion?

Yes.  Put ger into the Language Code column for Luxembourgish.  There is nothing to apply, hence it's inactive.

Paul said:

Put ger into the Language Code column for Luxembourgish.

Never thought of that! Thanks! 

This stuff is far more intricate than I figured...

And suddenly I UNDERSTAND! It's all clear to me now! Thank you for your patience! I think I now shall be able to explain also to others in my revised blog post. I shall send a link when I am done (but if you will hesitate to take a look, I more than understand ).

This is actually very satisfying in a strange manner; strange because it is not a big matter at all, I believe. (Not many users will need to avail themselves of this opportunity, I think.)

PS. I managed to find the old wikis (they had new URLs), and they were no help at all! But I still think the "old" way of showing the target in the form of a flag (for the project target language) and a language code (for the LW TM engine) is illustrative. (And I don't understand your comment "Completely different feature!"...)

And suddenly I UNDERSTAND! It's all clear to me now! Thank you for your patience! I think I now shall be able to explain also to others in my revised blog post. I shall send a link when I am done (but if you will hesitate to take a look, I more than understand ).

This is actually very satisfying in a strange manner; strange because it is not a big matter at all, I believe. (Not many users will need to avail themselves of this opportunity, I think.)

PS. I managed to find the old wikis (they had new URLs), and they were no help at all! But I still think the "old" way of showing the target in the form of a flag (for the project target language) and a language code (for the LW TM engine) is illustrative. (And I don't understand your comment "Completely different feature!"...)

 Mats Linder 

Mats Linder said:

I still think the "old" way of showing the target in the form of a flag (for the project target language) and a language code (for the LW TM engine) is illustrative. (And I don't understand your comment "Completely different feature!"...)

The feature you are describing has nothing at all to do with Language Mapping!  The language mapping feature has never used flags.

Just one more reply:

I realise that once the "mapping" has been made, the actual project's target language is irrelevant. But I still think that, as a reminder, it would make sense to indicate in some way that the target language in LW is not the one in the project. E.g. 

(lb-LU) ger

(dan) nor

or even 

No flags. (But the language mapping feature DID use flags at the time when I wrote my previous text. I did not create that image myself.)

Just to show how I was thinking.

Mats Linder 

Mats Linder said:

No flags. (But the language mapping feature DID use flags at the time when I wrote my previous text. I did not create that image myself.)

No, it didn't!

The image you are showing is not taken from the language mapping feature.  It's taken from the Language Weaver UI for the languages in the project.  That is purely a selector and nothing to do with language mapping.  I think you need to make this clear or you'll make everyone else as confused as you!

If you go to the Cloud-based reources you'll see they are still used:

But this is not the language mapping feature which is a feature to "fool" Trados Studio into using a completely different language for returning machine translation results.

I think this must stop here...  You need not fear that I shall confuse anyone with this since anyway I cannot reproduce the image I used, and I don't think I am confused any longer.

But what is still a mystery is that my old (four years) image not only looks more like the presentation in the Language Weaver Cloud presentation than the image you show, and -- in particular -- that the image I somehow managed to obtain has, for "Target", the Luxembourgian flag *together* with the "ger" language code! I doubt that would be possible to obtain in the dialog that you show.

Anyway, to me that is an unsolvable mystery which is no longer of any importance. I am sorry to have troubled you so much with this. (The main reason for my confusion was that I had not understood the difference between the Trados project language codes and the "mapping" codes. I'm pretty sure I do now.)

Paul said:

The language mapping feature has never used flags.

Sorry to intrude once again... But I just found an old document (don't know how old) called Language Mapping and Dictionary Support, where this image (and many similar ones) figures:

Anyway -- old stuff, so no need to comment.

PS. I found that this is actually the old wiki entry. For some reason I must have found another one, less appopriate, when I was looking for it and said they were "no use at all".

Hi Mats Linder 

Old stuff... but I have to comment ;-)

That does indeed say "Language Mappings" but I am fairly certain it isn't the same thing.  This is the best I can find to illustrate this... if you look at this KB article you can see a similarly old UI with flags and with the same source, target, model, dictionary... but with an additional button for "View Language Mapping":