BUG: the Okapi XLIFF filter for OmegaT ignores <empty> translations

[Manuel Souto Pico]

Dear all,

I'm flagging a issue with the XLIFF  that prevents the "Set empty translation" function in OmegaT from working.

I am sharing this here in the list first in case there is some discussion, I will create the ticket later.

# Preconditions

An OmegaT project with an XLIFF file, using the Okapi XLIFF filter.

      <trans-unit id="1" approved="yes">
        <source xml:lang="en">foo</source>
        <target xml:lang="xx">bar</target>
      </trans-unit>

# Steps

Translate one segment with an empty translation: in OmegaT, go to Edit > Set empty translation. The segment in the OmegaT editor will show <EMPTY>. This is different from an untranslated segment. 

Press Ctrl+D to generate the target file. 

# Expected results

The target segment in the target file is empty. 

      <trans-unit id="1" approved="yes">
        <source xml:lang="en">foo</source>
        <target xml:lang="xx"></target>
      </trans-unit>

# Actual results

The target segment in the target file contains the original target text. 

      <trans-unit id="1" approved="yes">
        <source xml:lang="en">foo</source>
        <target xml:lang="xx">bar</target>
      </trans-unit>

This is the same result as for a segment that has not been translated at all (where the target segment has no content). 

Let me know if any questions.

Cheers, Manuel