-
Bug
-
Resolution: Fixed
-
None
-
Critical
-
Fixed bug which caused inappropriate single tags parsing when id of tags are not the same in source and target
-
Emptyshow more show less
For transunit like
<trans-unit id="380" ax:state-name="Checked" ax:state-id="102" ax:state-flags="4194304"> <source><bpt id="1" rid="1" ax:s-id="9" ax:s-is-base-style="True" ax:s-font-name="SF Pro Text" ax:s-font-size="6.0" /><bpt id="3" rid="2" ax:s-id="10" /><x id="7" ctype="x-hex:DBC0" /><x id="8" ctype="x-hex:DC3F" /><ept id="4" rid="2" /><bpt id="5" rid="3" ax:s-id="1" /> Intended use<ept id="6" rid="3" /><ept id="2" rid="1" /></source> <target><bpt id="1" rid="1" ax:s-id="9" ax:s-is-base-style="True" ax:s-font-name="SF Pro Text" ax:s-font-size="6.0" /><bpt id="3" rid="2" ax:s-id="1" /><x id="5" ctype="x-hex:DBC0" /><x id="6" ctype="x-hex:DC3F" /> الغرض من الاستخدام (الاستخدام المقصود)<ept id="4" rid="2" /><ept id="2" rid="1" /></target> </trans-unit>
Single tags are processed wrong which causes that in the imported segment we have duplicated tags (</5></5> in this case) which prevents such a segment from editing, because of the duplicated tags error.
Need to fix this behavior.
- relates to
-
TRANSLATE-3893 Create a test for amended tags parsing code
- Selected for dev