Search Issue Tracker
Duplicate
Votes
0
Found in [Package]
1.0.0-pre.9
Issue ID
1342014
Regression
No
[Localization] exported XLIFF files are missing xml:space="preserve" element
How to reproduce:
1. Open the attached "case_1342014.zip" project
2. Select Window/Asset Management/Localization Tables and open its context menu (by selecting three dots)
3. Select Export/XLIFF
4. Open the exported .xlf file in the text editor and observe the inside of <trans-unit>
Expected result: it has xml:space="preserve" element to properly indicate that the string is containing non escaped "\n"
Actual result: it does not have xml:space="preserve" element
Reproducible with: 0.9.0-preview - 1.0.0-pre.9 (2019.4.28f1, 2020.3.13f1, 2021.1.14f1, 2021.2.0b2, 2022.1.0a1)
Could not test with: 2018.4 (could not downgrade)
Note: Reproducible with 1.2 and 2.0 XLIFF versions
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Add comment