Forum Discussion
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 line breaks or tabs that do not normally exist in my path. You have to delete them by hand in the translation tool.
And so when I re-import the translated and cleaned files, I lose my text formatting or I have [Object Object] tags that appear in my RISE module (see pj).
What to do to avoid this?
Thank you
Hi,
I tried something else. I exported an XLF file in English. I opened the XLF file in Notepad++ and only changed the title in English. Saved it and imported it back in again. It said successful, but the Title did not update at all...
Hi, Darren. I want to be sure Angelo received the questions you sent him. I took a look into your case (#02130548), and the last email was sent to you from Angelo on January 27. In that email, he recommended using Smartcat.ai, which generates XLIFF 1.2.
Do you have another case with Angelo? If so, what is the case number for that one?
I replied to his email twice yesterday and twice today with updates and questions. I also requested if it was possible to arrange a call. We have dozens of other users in the organization with the same situation and we want to resolve and find out what is the issue on whatever side. We have our own Translation Team and system that uses Systran for the Machine translation which he asked for. Not sure why we need to purchase another translation tool such as SmartCat.ai just to export 1.2? If Rise exports 1.2, and I only change one sentence and reimport it then the XLF file should still be 1.2? I am just trying to get my head around the correct process as we have hundreds of projects that are manual copy and paste.
Thanks, Darren. I'm sorry this has been a frustrating experience so far.
I'm going to have our Senior Support Engineers reach out to you to get you the help you need. I've shared all of this information with them, and you'll hear from the team soon.
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?
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!
Thanks for sharing those Trados tips, Loren!
Hello, Venkatesh. Thanks for sharing the steps you followed! It sounds like you didn't duplicate the course first before exporting the XLIFF file. That's step 1 in the translation process.
Also, an XLIFF file isn't meant to be translated manually, so you'll want to use a translation tool specifically for XLIFF files to translate your course. Lots of folks in the community have had success with a free tool called SmartCat, so you may want to give that one a try!
We are trying to translate English to French Rise course using the XLIFF tool, Trados. When we export the XLIFF file, it displays the text as paragraphs (text block from Rise) and not as individual sentences. We also opted for the HTML formatting and hence the paragraphs of text are embedded with the HTML tags making it difficult to translate. We have used Trados for Storyline translation and never had an issue since the text got separated into individual sentences and we could translate per unit (or sentence). With Rise, we are finding it difficult to translate blocks of text.
Our question is, are we doing something wrong here with the translation? Is there anything else we can do to separate the sentences or make this translation process more efficient using Trados? Any feedback or suggestions will be greatly appreciated. Thank you.
Hi Aishwarya,
Storyline 360 text boxes have different functionality than Rise 360 text blocks which is why you're seeing different translation units in your XLIFF. With Rise 360 right now, text blocks will continue to show as a single unit.
I'll defer to the community of users on how this works with Trados.
