Details
-
New Feature
-
Resolution: Unresolved
-
None
-
None
-
High
-
Empty show more show less
Description
So far we have context in translate5 based on segment-ID and resname, as implemented here:
https://jira.translate5.net/browse/TRANSLATE-3952
Now in addition we implement context based on the same previous and next segment in the translated document as implemented in t5memory with https://jira.translate5.net/browse/T5TMS-183
If we have a context match of this type, this scores as a 105% match.
If in addition the document-name is the same, it scores as 106% match.
If in addition the context-ID as implemented with -3952 is also the same, it scores as 107% match.
In addition the match-range and pricing configuration is extended by a config, that defines for each existing match-range scheme, which of the match types over 100% scores how much percent. Those types are:
- document name the same
- repetition
- document name and resname/segmentID the same
- terminology match
- context of previous and next segment the same
- context of previous and next segment the same AND document name the same
- context of previous and next segment the same AND document name AND document name and resname/segmentID the same
And important: If a segment is saved, for which more than 1 context match with same prev and next segments exist, show all that matches and their prev and next segments and the document name of them to the user and ask, which of them should be overwritten. For this the repetition editor can be reused.
Attachments
Issue Links
- relates to
-
TRANSLATE-3952 Use resname from xliff and if not set segment id from xliff in task as context for t5memory
- Selected for dev