Hi Kirill,

First of all if you have one template with DE->RU/UKR/EN/FR and you only want to handle DE->RU for example then this is no problem.  You just work on that pair and ignore the rest.  When you open the RU file it will automatically select the correct RU resources and won't store TUs in other TMs.

However!  If you do this then you are also waiting for Studio to process the batch tasks when you create the project for all the language pairs in the project and if you have many files this could lead to unnecessary waiting times... notwithstanding the additional files you will be creating every time.

I would say that if you don't always need to create Projects with all these languages in it because you always work with this many language pairs for every project that you just create templates for each language combination.  You only do it once and then life is easier.

If you sometimes create real multilingual Projects where you actually have to translate the files into multiple languages then why not create templates for those combinations too?  Might be a little effort to begin with but I think it makes sense.