Details
-
Bug
-
Resolution: Fixed
-
None
-
Medium
-
Across XLF may contain invalid segmented content for not translatable (not editable) segments. This is fixed by using the not segment content in that case.
-
Empty show more show less
Description
Problem
Across XLF may contain such content
<trans-unit id="327" translate="no" ax:state-name="KeepSource" ax:state-id="1" ax:state-flags="1024"> <source>Satz eins. Satz zwei.</source> <seg-source><mrk mtype="seg" mid="1">Satz eins.</mrk> <mrk mtype="seg" mid="2">Satz zwei.</mrk></seg-source> <target>Satz eins. Satz zwei.</target> </trans-unit>
This produces an error in translate5 since non translatable segments are still shown in translate5 and therefore the segmentation is wrong in this context.
solution
Desired solution depending on the effort: translate="no" segments should be imported in a way, so that it works, and should not be exported on export.
Attachments
Issue Links
- causes
-
TRANSLATE-2591 comments of translate no segments are not exported anymore
- Done
-
TRANSLATE-2776 XLF translate no with different mrk counts lead to unknown mrk tag error
- Done
- relates to
-
TRANSLATE-2384 Okapi does not always fill missing targets with source content
- Done