Segment set as <EMPTY> not empty in XLIFF

[ysavourel]

From Manuel (https://groups.yahoo.com/neo/groups/okapitools/conversations/messages/5564):

"If I set an empty translation (the target reads <EMPTY> in OmegaT), then when I generate the target file, the source text appears in the target segment. This is so even though I am using a customized filter parameters file ([e-mail])."

We need to check how <EMPTY> segments are provided by the API when merging back.

[Manuel Souto Pico]

I can confirm the trans-unit element looks identical both in the source and the target files, so no state set.

I can also confirm the the Okapi XLIFF filter is using a customized configuration file ([e-mail]) which contains the line allowEmptyTargets.b=true.

Thanks.

[Manuel Souto Pico]

Here comes an update.

I don’t reproduce this issue with the following setup:

• Version: OmegaT-5.7.1_0_c3206253
• Platform: Linux 5.16.0-6mx-amd64
• Java: 1.8.0_312 amd64
• Plugin version: okapiFiltersForOmegaT-1.12-1.44.0.jar (custom build based on commit c5fa867).

When I generate the target files, the segment with translation <EMPTY>in OmegaT appears as <target xml:lang="es"></target> in the target XLIFF file.

Shall I presume that someone worked on this ticket (perhaps as a side effect of other changes) but didn’t update its status?

[Manuel Souto Pico]

I can also confirm that the source text is used as the translation if I disable the property as allowEmptyTargets.b=false