- edited description
Protected entries in XLIFF show translation as source text
Preconditions
- Project with translated XLIFF file containing entries with
translate="no"
orstate="final"
. - Okapi filter plugin for OmegaT
Steps to reproduce
Go to XLIFF (Okapi) filter options and check (depending on the case):
- Show and protect entries with translate='no', or
- Protect entries with state='final', or
- both
That's already done in the project settings of the project package attached.
Expected results
- The entry is highlighted and the translation is locked.
- The text content of the
<source>
element has the source text:
source: baz
target: qux
Actual results
- As expected.
- The text content of the
<source>
element has the target text:
source: baz
target: qux
Comments
The feedback I got from OmegaT developers is that this issue is not directly OmegaT, all the transformations are done in the Okapi filter. As a matter of fact, this filter is explicitly replacing the source with the protected translation (the tooltip still show the original source text though).
See the ticket omegat-plugin#2 discussing the issue.
Comments (8)
-
reporter -
reporter - edited description
-
- changed status to open
-
- changed milestone to 1.46.0
-
assigned issue to
-
reporter Hi @Jim Hargrave just realized that this ticket should probably go in the omegat-plugin tracker, sorry about that. Could you please migrate it?
-
This appears to be an XliffFilter bug (or possible an unrelated bug). The serialized output has the TextUnits marked as
isTranslatable=yes
-
- attached sample_es.json.xlf.xliff_extracted
- attached sample_es.json.xlf.ser
- attached sample_es.json.xlf
<div class="preview-container wiki-content"><!-- loaded via ajax --></div> <div class="mask"></div> </div>
</div> </form>
-
- changed status to resolved
I drilled down and found everything is working correctly. ProtoBuf doesn't write our false variables to save space. ut round trip seems to work correctly.
- Log in to comment