You are currently working on UAT 

  • State Verified Answer
  • Replies 2 replies
  • Subscribers 429 subscribers
  • Views 744 views
  • Users 0 members are here
Options
Related

Not all TM settings are "cascaded" in projects with language-specific TMs

Yvonne Rezbach

Hello,

I just noticed by coincidence (luckily :-)):

If I have a project with different TMs per language, I can change the filter settings in the "all language pairs" area of the project settings and the change will be cascaded into all individual language pairs.

However, changing the field values in the "update" field whas not cascaded, i.e. the changed filed value was not taken over into the settings of the languages pairs.

What's the concept behind this? Which changes in the "All languages" area are copied automatically into the languages and which are not? It's a great feature if you are working with 20+ languages but this confusing and dangerous ...

Thanks

yve
Rate translation
×
Suggest better translation
×
Moderator UI
×
  • Get AI Suggestion
Parents
  • +1

    Hello

    This is a very good point.

    The settings related to he 'Update' fields are TM-specific. So in order to use a enter a field value, the field has to defined in the given TM's  settings. And as these parameters of a TM are unrelated to the settings other TMs. So when you are updating these fields, you have to update them on the given target language level - when using file-based TMs.

    On the other hand, if you are using GroupShare-based translation memories, this is much simpler. As those translation memories can hold together several languages pairs (as an umbrella TM, so to say), these field values are defined on the whole TM-level, and affect all language pairs under it. So you would only have to update these field values once.

    Hope this answers your question. In case anything is unclear please let me know.

    Best wishes,
    Greta
Reply
  • +1

    Hello

    This is a very good point.

    The settings related to he 'Update' fields are TM-specific. So in order to use a enter a field value, the field has to defined in the given TM's  settings. And as these parameters of a TM are unrelated to the settings other TMs. So when you are updating these fields, you have to update them on the given target language level - when using file-based TMs.

    On the other hand, if you are using GroupShare-based translation memories, this is much simpler. As those translation memories can hold together several languages pairs (as an umbrella TM, so to say), these field values are defined on the whole TM-level, and affect all language pairs under it. So you would only have to update these field values once.

    Hope this answers your question. In case anything is unclear please let me know.

    Best wishes,
    Greta
Children