I tried to dig a bit deeper.
I think this might have larger functionality implications
SDL does different things with whitespaces depending on that value. It's unclear what happens to the target element (I assume the attribute is maintained).
Is the XLIFF exported by QT libraries incorrect?
Looking at examples from Transifex and others, I noticed that the
xml:space attribute is defined on the
<trans-unit>, not on the
The XLIFF 1.2 specs have
xml:space attribute as optional on:
There's no mention of
I think we should morph this bug into a more generic "Handle xml:space in XLIFF file", and fix the VPN string as part of the export automation.