Forum Discussion

DavidNeuburger-'s avatar
DavidNeuburger-
Community Member
7 years ago

Xlif problems

Hello I have a lot of problem when I try to translate a xlif export of a route RISE. Indeed, when I open the export in a translation tool like smartcat.ai or SDL Trados Studio 2019, I oddly have lin...
rise 360
DarrenNash's avatar
DarrenNash
Community Member
6 years ago

Hi, the engineer reached out and I think we have a fix now. He noticed that the imported XLF files did not have the additional <target> tags with each <source> tag. Our Translation system only translated the text required and made no changes to any code which I was not aware of.

So instead of just <source>Title</source> you also needed <target>Title</target> with it and for every <source></source> in the document. This worked perfectly.

Another test I did now that I had a solution from now, on was to actually change the <source> to <target> tags and this works also.... might be useful for others that have been going through the same issues.

Not sure why Rise exports the XLF file with <source> tags only and then expects <target> tags in return?

Crystal-Horn's avatar
Crystal-Horn
Staff
6 years ago

Thanks for that update, Darren. Very helpful.

Standard translation software should add the <target> tag and the translated text to the XLF file. Only the <source> tag and text will be included when you export an XLF for translation because the translation service should add the rest!