Unable to set <EMPTY> translation in OmegaT with Okapi filter OpenXML
Issue #41
new
Preconditions
- Install the Okapi filter plugin for OmegaT, i.e. put the
okapiFiltersForOmegaT-1.9-1.41.0.jar
file in theplugins
folder of OmegaT. - Create an OmegaT project and add a Word file that contains at least a couple of sentences.
Steps to reproduce
- In the first segment, go to Edit > Set empty translation
- Move to another segment.
Expected results
- OmegaT displays
<EMPTY>
in the segment where the empty translation has been set. - When exporting the target Word file, there’s nothing in the position of that segment.
Actual results
- OK (as expected)
- When exporting the target file, there’s the source text in the position of that segment.
Additional info
The filter configuration file for the Okapi XLIFF filter has an option to allow for an empty translation, but I am not aware of any such option in the equivalent configuration file for the OpenXML filter (i.e. okf_openxml@foo.fprm
).
Comments (1)
-
reporter - Log in to comment
Transferred from Okapi issue #1055