• State Suggested Answer
  • Replies 10 replies
  • Answers 2 answers
  • Subscribers 433 subscribers
  • Views 3220 views
  • Users 0 members are here
Options
Related

"Include only relevant resources when creating a project package" doesn't seem to work...

Lieven Lannoo

Hi,

Having migrated from 2014 to 2017, we were looking forward to the "Include only relevant resources when creating a project package" feature. This doesn't seem to work for us, however. When creating a project with 2 target languages and a separate TM for each of those languages, the project package for either one of the target languages still contains the TM for the other target language. Are we missing something? These are not AnyTM memories, by the way, but file-based TMs. 

Many thanks,

Lieven
Rate translation
×
Suggest better translation
×
Moderator UI
×
  • Get AI Suggestion
Parents
  • 0
    You should not specify the TMs in the "All languages" configuratiobn, but in the respective language-specific configurations.
    Then the packages will contain only TMs relevant for the respective languages.
  • 0 in reply to Evzen Polenka
    Thanks for pointing out the workaround Evzen.

    Paul Filkin | RWS Group

    ________________________
    Design your own training!
    You've done the courses and still need to go a little further, or still not clear? 
    Tell us what you need in our Community Solutions Hub

  • 0 in reply to Paul
    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).

    I admit that this requires somehow deeper knowledge of how Studio works and a certain degree of "technical imagination"... and given the average "knowledge" of average Studio user, it's not very intuitive in the end...
  • 0 in reply to Evzen Polenka

    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

    Paul Filkin | RWS Group

    ________________________
    Design your own training!
    You've done the courses and still need to go a little further, or still not clear? 
    Tell us what you need in our Community Solutions Hub

  • 0 in reply to 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 :-\
  • 0 in reply to Evzen Polenka

    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

    Paul Filkin | RWS Group

    ________________________
    Design your own training!
    You've done the courses and still need to go a little further, or still not clear? 
    Tell us what you need in our Community Solutions Hub

  • 0 in reply to Paul
    Well, let's see it from user's perspective - they don't differentiate between "GroupShare" and "Studio"... User simply "uses Studio with TMs" and that's it. They don't care about 'the tech stuff' behind... They simply "add TMs to project". Done.
    And that "added TM" is multilingual from the user's perspective... as can be clearly seen in Studio(!) when I open server TM - Studio offers me a list of language pairs 'contained' in that TM. And even in GroupShare web interface I see that TM as SINGLE TM containing multiple language pairs, not as multiple separate TMs.

    As for the reasons for the language-specific settings - okay, then I know all that... I thought you mean yet something else. All clarified.
Reply
  • 0 in reply to Paul
    Well, let's see it from user's perspective - they don't differentiate between "GroupShare" and "Studio"... User simply "uses Studio with TMs" and that's it. They don't care about 'the tech stuff' behind... They simply "add TMs to project". Done.
    And that "added TM" is multilingual from the user's perspective... as can be clearly seen in Studio(!) when I open server TM - Studio offers me a list of language pairs 'contained' in that TM. And even in GroupShare web interface I see that TM as SINGLE TM containing multiple language pairs, not as multiple separate TMs.

    As for the reasons for the language-specific settings - okay, then I know all that... I thought you mean yet something else. All clarified.
Children