Match % < 100 + unchecked 'different context' has no result

Description

If the match percentage is less than 100, the context must be different (as the resid is generated from the content hash in most cases). So having chosen 80/90%, the Different Context checkbox should be automatically checked and greyed out.

Otherwise, the user might think something actually happened, particularly if they don't understand contexts.

Environment

None

Activity

Show:

Former user 2 August 2018 at 01:30

https://github.com/zanata/zanata-platform/pull/449
Original issue not valid for all cases: In most cases, resId is generated from the content hash, but this depends on the source format. This won't be true for eg Properties files, nor for Gettext entries which have msgctxt.

Sean Flanigan 1 August 2017 at 01:35

If the match percentage is less than 100, the context must be different (as the resid is generated from the content hash in most cases)

In most cases, resId is generated from the content hash, but this depends on the source format. This won't be true for eg Properties files, nor for Gettext entries which have msgctxt.

For the common case where the resId is just a hash of the content, yes, context is mostly meaningless if you're also comparing the text. But in other cases it can be quite important, especially if the text isn't an exact match.

Former user 26 July 2017 at 00:00

Automatically checked different context means, once user select less than 100% match, they have to accept translation with different context, as fuzzy. What if they want to reject translation less than 100% and with different context? resId for properties files is the properties key, for example:

will have less than 100% match, but same context between 1 and 2, different context between 2 and 3. In this example, between 2 to 3 you may want to reject translation (different context) but between 1 and 2 you may want to save as fuzzy.

Won't Fix

Details

Assignee

Reporter

Labels

Tested Version/s

Components

Affects versions

Priority

More fields

Created 25 July 2017 at 05:14
Updated 2 August 2018 at 01:30
Resolved 2 August 2018 at 01:30