Details
-
Improvement
-
Resolution: Unresolved
-
None
-
None
-
High
-
Use the text content of Placeables also when requesting MachineTranslation Engines to improve the translations
-
Empty show more show less
Description
Problem
With content protection and runtimeOptions.import.xlf.placeablesXpathes we can produce placeables, that stand for actual text that is part of the sentence, that should be translated.
When you send this text to an MT or LLM, the text for the MT looks like a cloze text (Lückentext) and it has to guess, what parts are missing to translate correctly the rest
Solution
When MTs are requested, instead of sending a placeable we should send a tag pair, that encapsulates the text-content the placeable stands for. When receiving the translation back, we replace the tag pair and its content again with the placeable.
Problems might be
- the tag is lost or ripped apart by the MT
- more text then the required one is placed within the tag pair
The first problem needs to be solved by using the existing tag repair and place the placeable in the most likely position.
The second problem needs to be identified and solved by the post-editor.
Attachments
Issue Links
- blocks
-
TRANSLATE-3945 Check coverage of existing API-tests and list them here
- Selected for dev
- is blocked by
-
TRANSLATE-3683 when source segment is edited it will be shown in target visual
- Done
-
TRANSLATE-4101 Enhancements for visual as ordered by translate5 Consortium Milestone III
- In Progress
- relates to
-
TRANSLATE-3884 Use new possibilies to respect context with DeepL
- Selected for dev
-
TRANSLATE-4203 DeepL: Switch tag-handling to be able to send tags as xliff tags and whitespace tags as plain whitespace
- Selected for dev
-
TRANSLATE-4490 Check GPT tag handling
- Selected for dev
- mentioned in
-
Page Loading...