Moreover: when I select Any TM option, I get this print-screen showing and English to Czech pair, but a French flag!

What is wrong?

Thank you,

Milada

Milada Šejnohová (MiladaŠejnohová) 

There is nothing wrong.  You created a French to Czech project:

When you add AnyTM it allows yo to use a TM in any language at all, but it will still be a French to Czech project.  So the languages reflect the languages of the project, not the TM.

Milada Šejnohová (MiladaŠejnohová) 

The reason is very simple: you are still in the FR-CS project.

The reason for so many TMs listed in your view is quite simple: these are all TMs you ever used before. All this trouble is caused by using "Translate single file approach". It seems to be the most simple way to work with Trados, but it ends in being the most complicated one because of the chaos it creates, when used the way you do it.

If you wish to continue working that way, do the following:

• Go to File -> Options -> Language pairs and REMOVE all TMs listed under All language pairs.
• Now go to each language pair listed there, click the setting for TMs and add the TMs corresponding to the language pair there. You need to activate the option shown in the screenshot below for each and every separate language pair.
• Do this for all your language pairs listed there.
• Remove all unused language pairs.
• NEVER add a TM under All Language Pairs anymore!
• When you now select the proper language pair for your translatable file, Studio will select the corresponding TMs automatically.

Or simply start using project templates, where you can configure all settings for the necessary language pair.

Milada Šejnohová (MiladaŠejnohová) 

In addition to what Jerzy mentioned, which is all correct, I just want to note on this:

Milada Šejnohová said:

What am I doing wrong?

You are doing nothing wrong! This is a bug in the 2022 version which mostly manifests itself when using the single document workflow (the one you are using to open files for translation).  Once the file is open, if you go back to the Projects View you will see that a different project is still selected.  So when you go to your project settings you are actually looking at the wrong project.  To correct this you need to select the correct project and then hit the enter key, or just double click the project.  Now your project settings will be correct.

This has been reported already.

Loredana Stoia fyi.

Hi Jerzy,

thank you for explaining me the reason.

I have watched the video called "Getting started with Trados 2022 Part 1" at https://www.youtube.com/watch?v=5j9iRBLMBFY&ab_channel=TranslatorsTechCorner

Is this what you have meant by saying to start using project templates? (I looked at this link, too: https://gateway.rws.com/csm?id=kb_article_view&sysparm_article=KB0027680).

Thank you foryour answer.

Milada Šejnohová

Thank you Paul, too for your help,

Milada

Milada Šejnohová (MiladaŠejnohová) 

Yes. But using your existing projects to build project templates will not be the best idea, as this will keep the TM mess you have now. Better idea would be creating new projects from scratch for each language pair and possibly each customer separately.

I followed the steps described in the video I sent you the link to. Do you mean that what this video author suggests is a mess, too?

If yes, please provide a step-by-step guide how to do it your way. I checked the link https://gateway.rws.com/csm?id=kb_article_view&sysparm_article=KB0027680 but it di not help me any further.

Thanks.

Milada Šejnohová

Milada Šejnohová (MiladaŠejnohová) 

Sorry, I have no time to look into the video.

There are many tutorials on the web how to use projects. Unfortunately, this here is not a place where I could train you.

I did not and do not request any training from you. 

It´s about a decent language that you - as it seems - are not familiar with.

The only thing I requested from you was being decent to me at least for the reason that I paid for this software, too and that I am your customer. You should be here for me, not me for you.

And as a Slav (I suppose you are Polish), you should be familiar with the fact that my name is female, so that I am a woman. And at least from this fact as a man you should be polite to a woman.

Jerzy Czopik 

I'm sorry, but I think you misunderstood something here. I am a freelance translator like you and give my time for free here to help others. I am in no way obliged to do so. And I fail to see where my language hasn't been decent. I might have written things in a very direct way, but this saves time and my no means is meant to hurt or offend anyone.

 Milada Šejnohová (MiladaŠejnohová) 

I just wanted to clarify a few things.  Jerzy does not work for RWS he is another user, like you.  He is a very experienced one and often offers his views on how the software should be used.  I think in this case he probably read your question on whether the video was a good one or not as a request to evaluate the best way to learn.

I looked at the video and it looks fine to me.  I think both Jerzy and myself assumed you were using the single document workflow as this is the most common reason for seeing the problem you originally outlined.  This is not the approach in the video.  This screenshot you provided is the single document approach:

But I can also see you are using a mix of approaches:

There is nothing wrong with this at all as they all have their strengths and weaknesses.  But working with project templates, which is what Jerzy suggested, does carry some advantages in that you can manage your TMs in a more efficient way for each project and develop a more consistent approach to your work.

I think if we come back to your original questions...

Milada Šejnohová said:

What to do in order NOT to use Any TM option.

This problem is not your fault.  It's caused by a bug in Trados Studio 2022 which shows the project settings for the selected project as oppose to the one you are in.  This normally manifests itself when working with the single document workflow so you need to be aware of this and go back and select the correct project before opening the project settings... even though you have opened the file for translation and are clearly working on the right file.  Definitely something we have to fix.
Working with studio projects as opposed to the single document workflow would always avoid this problem.

Milada Šejnohová said:

Is this what you have meant by saying to start using project templates?

Sort of.  In the video the approach taken does use a "normal" studio project, but the creator is using the default template.  However, towards the end of the project creation he does mention, and also recommends, using project templates starting off with saving the settings for the one he created as a custom template:

If you use custom templates then you can select them when you create a project and they will already have the TMs you need, termbases you need etc. which not only saves time but it also ensures you will have the consistently correct resources you need for your projects.

On this part...

Jerzy Czopik said:

But using your existing projects to build project templates will not be the best idea, as this will keep the TM mess you have now. Better idea would be creating new projects from scratch for each language pair and possibly each customer separately.

I don't necessarily agree with this statement.  The end goal is correct, but you can get there by using existing projects.  Once you have created your project template you should be able to easily edit it and remove the resources you don't need.  But starting clean does indeed have its advantages.

 Milada Šejnohová (MiladaŠejnohová) 

I just wanted to clarify a few things.  Jerzy does not work for RWS he is another user, like you.  He is a very experienced one and often offers his views on how the software should be used.  I think in this case he probably read your question on whether the video was a good one or not as a request to evaluate the best way to learn.

I looked at the video and it looks fine to me.  I think both Jerzy and myself assumed you were using the single document workflow as this is the most common reason for seeing the problem you originally outlined.  This is not the approach in the video.  This screenshot you provided is the single document approach:

But I can also see you are using a mix of approaches:

There is nothing wrong with this at all as they all have their strengths and weaknesses.  But working with project templates, which is what Jerzy suggested, does carry some advantages in that you can manage your TMs in a more efficient way for each project and develop a more consistent approach to your work.

I think if we come back to your original questions...

Milada Šejnohová said:

What to do in order NOT to use Any TM option.

This problem is not your fault.  It's caused by a bug in Trados Studio 2022 which shows the project settings for the selected project as oppose to the one you are in.  This normally manifests itself when working with the single document workflow so you need to be aware of this and go back and select the correct project before opening the project settings... even though you have opened the file for translation and are clearly working on the right file.  Definitely something we have to fix.
Working with studio projects as opposed to the single document workflow would always avoid this problem.

Milada Šejnohová said:

Is this what you have meant by saying to start using project templates?

Sort of.  In the video the approach taken does use a "normal" studio project, but the creator is using the default template.  However, towards the end of the project creation he does mention, and also recommends, using project templates starting off with saving the settings for the one he created as a custom template:

If you use custom templates then you can select them when you create a project and they will already have the TMs you need, termbases you need etc. which not only saves time but it also ensures you will have the consistently correct resources you need for your projects.

On this part...

Jerzy Czopik said:

But using your existing projects to build project templates will not be the best idea, as this will keep the TM mess you have now. Better idea would be creating new projects from scratch for each language pair and possibly each customer separately.

I don't necessarily agree with this statement.  The end goal is correct, but you can get there by using existing projects.  Once you have created your project template you should be able to easily edit it and remove the resources you don't need.  But starting clean does indeed have its advantages.