Details
-
Bug
-
Resolution: Unresolved
-
None
-
None
-
High
-
Empty show more show less
Description
Problem
The logic which checks which terms should be used for pre-translation is very basic and it allows also for example deprecated for pre-translation.
- If term will be used as translation depends on the usage status. Only prefered and permited terms will be used ( preferred terms > permitted terms).
- In case of 2 or more result in the target: always the first match will be used. Here the same logic as above regarding the statuses: prefered and permitted are allowed (prefered > permited)
The way how it should work regarding the status filtering should be taken over from the DeepL glosarry term upload.
In addition to that, move the status filtering logic from the Analisis.php class.
Attachments
Issue Links
- blocks
-
TRANSLATE-3511 Create missing Unit tests for ZfExtended ACL functionality
- Selected for dev
- is blocked by
-
TRANSLATE-3952 Use resname from xliff and if not set segment id from xliff in task as context for t5memory
- Selected for dev