Unknown said:

Actually it has always been my understanding that the current behavior is intentional and by design.
The "All languages" section is intended - as the name suggests - for configuring TMs for _ALL_ languages (i.e. it makes sense to have only MULTIlingual TMs here... and since file-based TMs are only MONOlingual, it does not make sense to put any TMs here... unless it's a monolingual project, of course).

Hi Evzen,

Not mine.  I remember this coming up years ago and I do think this is incorrect behaviour.  Studio doesn't have the concept of a multilingual TM as you point out and adding an incorrect TM to a package makes no sense at all unless you used AnyTM.  The deeper knowledge might help you see why the workaround is effective, but not why it should not be fixed to work in both scenarios.  The specific languages are for a very different reason.

Regards

Paul

Unknown said:

Actually it has always been my understanding that the current behavior is intentional and by design.
The "All languages" section is intended - as the name suggests - for configuring TMs for _ALL_ languages (i.e. it makes sense to have only MULTIlingual TMs here... and since file-based TMs are only MONOlingual, it does not make sense to put any TMs here... unless it's a monolingual project, of course).

Hi Evzen,

Not mine.  I remember this coming up years ago and I do think this is incorrect behaviour.  Studio doesn't have the concept of a multilingual TM as you point out and adding an incorrect TM to a package makes no sense at all unless you used AnyTM.  The deeper knowledge might help you see why the workaround is effective, but not why it should not be fixed to work in both scenarios.  The specific languages are for a very different reason.

Regards

Paul

Unknown said:

Studio doesn't have the concept of a multilingual TM

Not really... the server TMs are multilingual. And it has always been my understanding that the "All languages" is actually intended for these multilingual TMs.
(Actually even the filebased TMs CAN technically be multilingual... the internal database structure is ready for that)

If you say that the concept is different and that the specific languages sections are there for very different reason, then either me or the documentation is terribly missing something important for quite a number of years :-\

Unknown said:

Not really... the server TMs are multilingual.

Not really.  First of all this is GroupShare and not Studio, and secondly you are talking about a "holder" a level up.  The actual TMs within it are bilingual.  It's not like a TMX that could contain many languages inside the same TM structure.  Even if they can technically be multilingual, and I guess they could technically hold terminology as well if you extended it enough, Studio is not designed to use them this way.

The reason for the specific languages is to support different settings on each individual TM.  If you're happy with defaults, or one size fits all, then using All Languages means you only have to add the TMs, change settings, once and in one place.  If you use specific language pairs then you can set different search settings, penalties, field update values, auto-substitution settings etc. for each TM.

The help does say all of this, and does mention multilingual TMs on a server but this is really just a fast way to add one reference to multiple bilingual TMs.  If they were filebased then you would have to add them all one at a time into the All Language Pairs.  But either way you could then change the individual TM settings in the specific language pair.

All in here: https://docs.sdl.com/LiveContent/content/en-US/SDL%20Trados%20Studio%20Help-v4/GUID-D993EAEC-1DE5-49C3-8DC4-D6CACB2252BD