• State Suggested Answer
  • Replies 1 reply
  • Answers 1 answer
  • Subscribers 434 subscribers
  • Views 559 views
  • Users 0 members are here
Options
Related

Studio 2021, Autopropagation is not working for some projects

Jerome Roy

Hello All,

I've already search in some posts but could not find any hint for this issue:

In some projects given by my clients, autopropagation doesn't work.

For exemple, in my own projects:

if I confirm "ABC 1" Studio fills and confirms "ABC 2", "ABC 3" and so on.

If I confirm "1" in a segment, then all segments wirh only numbers are confirmed

Screenshot of Trados Studio showing translation results with segments 397, 399, 403 not filled or confirmed despite similar segments being autopropagated. Blue circles highlight the unconfirmed segments.

But, as you can see on this picture:

Segments 397, 399, 403 for example  are not filled and confirmed.

It only happens by client's project, not my own, my clients say they don't have any special settings on their side.

My settings for AP are the usual

Any idea where it could come from?

Thanks,

J. Roy

Generated Image Alt-Text
[edited by: Trados AI at 6:30 AM (GMT 0) on 29 Feb 2024]
emoji
Rate translation
×
Suggest better translation
×
Moderator UI
×
  • Get AI Suggestion
Parents
  • 0

    Hi 

    This happens to me sometimes, too. 

    My guess is that there is some hidden property to the segments that didn't autopropagate that makes them slightly different, and the software doesn't pick them up as 100% matches because of that.

    There is 'background content' that isn't displayed but is read (or attributed?) by the software when creating or working on projects. I don't claim to understand this, a Trados expert explained it to me once a long time ago when I was having problems with new 'identical' duplicate TUs being created instead of just the original TU being updated with my changes. Thus, I always assume any other 'invisible differences' where content should be identical are down to these background properties, which he called hex values.

    Sorry this isn't a solution. Maybe someone at RWS could take a look at the file to check what is behind this behaviour.

    All the best,

    Ali Smiley
    emoji
Reply
  • 0

    Hi 

    This happens to me sometimes, too. 

    My guess is that there is some hidden property to the segments that didn't autopropagate that makes them slightly different, and the software doesn't pick them up as 100% matches because of that.

    There is 'background content' that isn't displayed but is read (or attributed?) by the software when creating or working on projects. I don't claim to understand this, a Trados expert explained it to me once a long time ago when I was having problems with new 'identical' duplicate TUs being created instead of just the original TU being updated with my changes. Thus, I always assume any other 'invisible differences' where content should be identical are down to these background properties, which he called hex values.

    Sorry this isn't a solution. Maybe someone at RWS could take a look at the file to check what is behind this behaviour.

    All the best,

    Ali Smiley
    emoji
Children
No Data