Forum Discussion
Machine translation via XLIFF
We've got a large course which we need to translate into Spanish, Portuguese and Russian. We've exported the xliff file from SL360 (v3.68.28887.0) and ran it through a machine translation. I can s...
Thank you Jürgen Schoenemeyer That's worked.
The ".Name" vs "non-.Name" appears to come down to whether the datatype is "plaintext" (includes .Name") or "x-DocumentState" (doesn't contain ".Name") so I've not fiddled with those in themselves. What my chosen translation tool has done however is to replicate the id attribute from the <trans-unit> element down into the <source> and <target> elements. This seems like a bad idea in my opinion - not only because it is unnecesary, but also because an xml file should only contain unique id attributes.
Either way, stripping the extra id attributes from the <source> and <target> elements and removing the empty namespace attributes as you suggest has fixed the problem. I can write a console app to parse the translated output and patch these for our authors to use.
Thanks again.
@Chris,
One other thing to look at is it to see if the software you're using supports XLIFF 2.0. I've found Storyline handles this format more reliably than 1.2.
