Protected entries in XLIFF show translation as source text

Issue #1323 resolved
Manuel Souto Pico created an issue

Preconditions

  • Project with translated XLIFF file containing entries with translate="no" or state="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

  1. The entry is highlighted and the translation is locked.
  2. The text content of the <source> element has the source text:

source: baz
target: qux

Actual results

  1. As expected.
  2. 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)

  1. Manuel Souto Pico 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?

  2. jhargrave-straker

    This appears to be an XliffFilter bug (or possible an unrelated bug). The serialized output has the TextUnits marked as isTranslatable=yes

  3. jhargrave-straker

    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.

  4. Log in to comment