-
Bug
-
Resolution: Fixed
-
Neutral
-
3.4.2
-
None
-
None
Steps to reproduce
- Create a component on a Page which has i18n fields, e.g, a TextAndImage component
- At the Headline Text (or any other i18n field) fulfill something in english
- Check at JCR that only default property has value (field_DE or whatever doesn't even exist)
- Go to Translation Extended and translate it as XLIFF
- Check that at the trans-unit the target has the same value than in English (when it should be empty)
Expected results
The target tag exists, but it is empty
Actual results
The target tag has the same value than the fallback
Workaround
N/A
Development notes
The XLIFF I got:
myXLIFF.xml
<trans-unit extradata="2022.01.12 16:47:53 471" id="33a14dc7-427e-4d18-9e45-16d127ef955b:headline.i18n." resname="Text and image: Headline"> <source xml:lang="en">Headline English</source> <target xml:lang="de">Headline English</target> <note>http://localhost:8080/magnoliaAuthor/fallback/tagSelector.html</note> </trans-unit>
The XLIFF the CORE (NO CTSX) returns:
core-XLIFF.xml
<trans-unit extradata="2022.01.12 16:47:53 471" id="33a14dc7-427e-4d18-9e45-16d127ef955b:headline.i18n." resname="Text and image: Headline"> <source xml:lang="en">Headline English</source> <target xml:lang="de"/> <note>http://localhost:8080/magnoliaAuthor/fallback/tagSelector.html</note> </trans-unit>
Acceptance criteria
- mentioned in
-
Page Loading...