XML

Word

Printable

Urgency:
Critical
Important release notes:
The match-rate in the editor for repetitions is now 102% as defined and not any more the original percentage from the repeated segment. This is now the same behaviour as it is already in the analysis.
ChangeLog Description:

Hide
It could happen that repeated segments were blocked with a matchrate >= 100% but no content was pre-translated in the segment. Also the target original field was filled wrong on using repetitions. And the match-rate for repetitions is now 102% as defined and not original the percentage from the repeated segment. This is now the same behaviour as in the analysis.

Show
It could happen that repeated segments were blocked with a matchrate >= 100% but no content was pre-translated in the segment. Also the target original field was filled wrong on using repetitions. And the match-rate for repetitions is now 102% as defined and not original the percentage from the repeated segment. This is now the same behaviour as in the analysis.
Checklist:

Empty

show more show less

problems

In some circumstances using internal fuzzies it could happen that repeated segments were set to locked with 100% or higher but no translated content was added
when using the repetitions on translations, the target original text was filled wrong, since the field is hidden by default probably no one has seen that
The match rate on using repetitions was retrieved from the original segment. So if the original segment was translated with a fuzzy TM match, the here calculated match rate was also used for its repetitions. But in the analysis the repetitions were counting as 102%. Therefore the repetitions are now also getting 102% matchrate in the editor when using them.
1. On implementation of this issue the above sentence nr. 3 was correct, but is now superseded by ~~TRANSLATE-2834~~

causes

TRANSLATE-2801 Do not update matchrate on repetitions for review tasks

relates to

TRANSLATE-2834 Change repetition behaviour in pre-translation