Details
-
Bug
-
Resolution: Fixed
-
None
-
Critical
-
Empty show more show less
Description
problem
The okapiwhitespacebug-de-en.idml file attached to the linked issue TS-67 produces the following transunit in the generated XLF for export:
<trans-unit id="P8DD502D-tu1" xml:space="preserve">
<source xml:lang="de"> </source>
<target xml:lang="en"></target>
</trans-unit>
This empty target leads Okapi to crash. (Probably a <target /> would not.)
Multiple problems are to be solved here:
- If <target /> would be correct here for Okapi, we may not export
<target xml:lang="en"></target> but must convert that to <target /> form - The user does not see, that the source contains one space, and may not even touch the segment
- If the user tries to save the segment with just a whitespace, this whitespace is removed on saving, so this leads again to empty <target></target> With a non breaking space everything works, this was the workaround here.
- Why was this segment imported at all? This should be excluded since containing no text. (see FIXME problem mit translation task recognition)
In translate5 it looks like: