• State Suggested Answer
  • Replies 2 replies
  • Answers 1 answer
  • Subscribers 435 subscribers
  • Views 1010 views
  • Users 0 members are here
Options
Related

When I change a field value during a project translation, the modified field is added instead of overwriting the existing field if I have already confirmed the segments.

Beatriz de Vega

When translating a text in Studio, I add custom fields and values during the project creation. However, I sometimes want to modify one of the field values (that I specifically added during the project creation, not one that was already there from a previous match) and I would like the modified field value to overwrite the original one. However, if I have already confirmed a segment, the modified field value is added instead of overwriting the existing value. I understand that a new value gets added when the existing value came from a previous existing match in the TM that I reuse, but why does it not overwrite the original value in the same project (that I have not finalized), in the same context?

For a bit of context: translators would like to add the mention _rev to a field value if their text is revised, but they don´t always know if they are going to be revised after they are already well advanced in their translation, so they create their project without adding _rev and then they modify that value and add it once they know. Having both values added creates a lot of noise and reduces the space available to see more matches. 

Is there a setting somewhere that I am missing or is this normal behaviour?

Thanks.

Beatriz

Trados Studio interface showing a translation segment with a warning message about changing a field value during project translation.

Generated Image Alt-Text
[edited by: Trados AI at 7:42 AM (GMT 0) on 29 Feb 2024]
emoji
Rate translation
×
Suggest better translation
×
Moderator UI
×
  • Get AI Suggestion
Parents Reply Children
  • 0 in reply to Elisa Maxim

    Thank you for your reply Elisa. There are two translation memory fields in our memory where we want to have multiple values (Description and Request #/TR ID) since the same TU may be used by different TRs and in different projects/requests and we need to know it. It makes sense that if my TM allows for multiple values, these will be added in most of the cases (reused match from the same or a different TM, while importing files, etc.). However, I would have expected that if I have exactly the same source/target, with the same context, in the same project (not yet finalized), if I change mid-translation the field value in the Project settings, the modified field value would overwrite the original value when I reconfirm the segment, even in a TM with multiple values enabled. If this is the logic for the text of the segment (if I change my target in a project the new version automatically replaces the previous one) , why wouldn´t it work the same way for field values within the same project? Isn´t there a way to achieve this? We need to add some values when we create a project, but sometimes we have to change them mid-translation. Thanks.
    Beatriz 
    emoji