Xlif problems

Dec 07, 2018

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

46 Replies
Belkin International - EMEA

Hi Martika,

We are also experiencing the same issue on our side. The .xlf exported is not usable in our translation softwares (SDL WorldServer or SDL Studio 2017).

Do you have a quick workaround?

The only short-term solution for us is to copy-paste the content into a Word document which is really time consuming and not handy at all.

Thank you in advance for your reply.

Best regards,


Julien Theler


We have the same issue. We have two module to launch in 15 languages. We thought that the translation process in Rise was reliable, and we are very disappointed to see that a critical problem has been pending for more than 3 months. This cause Articulate Rise to be inappropriate for multilingual projects !

Do you really have no solution, at least one workaround?

Allison LaMotte

Hi Julien,

I'm so sorry you're experiencing this issue, I understand how frustrating it must be.

Unfortunately, I don't have any updates to share at this time, but you are now subscribed to this conversation which means as we share updates here, you’ll automatically be notified.

In the meantime, if there's anything else I can do to help, please let me know!

sven Ringger

Am I the only one who feels that the bugs and problems reported on this forum systematically seem to be answered by bots? Always the same answer "we will forward to our support", under the understanding that with a little luck a member of the community will bring free solutions. Hey Articulate, your product is a commercial product that you sell expensive, your customers are entitled to get concrete answers to the problems that your product imposes on them. A bug is not a request for functionality to prioritize according to your development backlogs, they are problems to solve all the more quickly as they are blocking for YOUR CLIENTS!!!! The problem described above by Julien has been lying around for months on your forum and has still not been solved. It involves very high manual intervention costs, and for any answer Articulate answers "we are looking into it"??? It's not serious and personally I wonder if we can really continue to recommend Articulate to our customers. Other solutions exist on the market and offer serious support. It would be time for Articulate to rebalance their staff between marketing and developers. The latter must not be very numerous....

a customer for many years but who is at the end of his patience

Justin Grenier

Hello, everyone.

Thanks for weighing in to let us know how important it is for us to get XLIFF translation right in Rise. We hear you, and we understand this is impacting you. Our team will be reaching out to each of you directly to schedule some focused time to get your feedback on the best way to fix this.

You'll hear directly from our team today.

Allison LaMotte

Hi everyone,

Some of you have told us that the tags we add to XLIFF exports (to preserve formatting) make those files hard to work with. 

If you’re one of those people, I’ve got some great news! You now have the option to discard that formatting in order to make XLIFF files easier to work with. Here’s more information on how that works. 

Keep in mind that if you decide not to include these HTML tags, any custom text formatting (size, color, boldness, etc.) that you’ve applied will be lost when you import your translation.

We've also reduced extra spaces in the export files so that they work better with third-party translators.

We’re hoping that these changes will relieve the pain that some of you have been experiencing with translation in Rise.

Thanks for your patience as we worked on this solution! 

Let me know if you have any questions.

Alyssa Gomez

Hi Suzannah!

Have you tried discarding the formatting to make XLIFF files easier to work with?

Here's how:

  1. Click Settings in the upper right corner and go to the Translations tab.

  2. Deselect Include HTML formatting.

  3. Click Export XLIFF File and save the file to your computer.

  4. Translate the file in the tool of your choice.

  5. Import the translated XLF file back into Rise 360.

Let me know how it goes!

Marco Baldan

Hello there, 

in the past we used the export function of an xlf file and could insert the data into the online tool we use for translation flawlessly.
With our latest submission we followed the same procedure. Unfortunately the developers of the translation services noted an issue arising with parts of the Html code: sometimes the text is cointained inside a block of html and not easy to display thus translatable. (see screenshot)

Have you encountered any such problems? I ask the question both to @articulate support and @other users.

We would like to avoid issues like this in the future: the ad-hoc solution they had to deploy costed extra time. 
Thank you very much for your attention



How the xlif file looks like sometimes

Crystal Horn

Hello, Marco! When you export your course for translation, do you have the option checked to "include HTML formatting?"

Choosing that option will add extra HTML tags to keep your text formatting. You can try deselecting this option if it's causing extra work for the translation provider. Keep in mind you'll need to reformat text in the translated version of your course.

Marco Baldan

Hello Crystal, 

thank you for your answer. I am positive that I had left the option clicked so that the text kept the HTML formatting.
I would like to ask you an additional question: What happens to a file without the HTML tagging when its translation is out back into Rise?  This would be my next question.
I sense a lot of manual work after that to make it again coherent with the initial design.


Alyssa Gomez

Hi Marco!

If you uncheck the "include HTML formatting" option, this exports your content in easy to translate blocks of text. However, it doesn’t contain the coding necessary to maintain any formatting you’ve applied to that content.

You're correct that you would have to go back and apply all of the text formatting, such as text color, size, and emphasis.

Crystal Horn

Hi there, Julie. I'm sorry you're hitting some speed bumps with using translation tools. We don't endorse using one tool over another because of their different features and support.

But, to get some better community help, can you let us know what kinds of challenges you're seeing? If you want to share a quick Peek 360 screencast of where it's not working for you, all the better!

Suzannah White

The fix for {object object} upon importing back into RISE that worked for me is:

For Trados Studio 2017/2019 users, please ensure the following settings are used:

  1. Enable the option “Do not store segmentation information in the translated file” in both areas of Trados Studio. 
    • Go to:  File > Options > XLIFF > Settings > Do not store segmentation information in the translated file
    • Go to: Project Settings > File Types > XLIFF > Settings > Do not store segmentation information in the translated file
  2. Use the Tag Verifying function to confirm there’s no tag errors

No more [object object] issues.  

Crystal Horn

Hi there, Joanna. Which translation software are you using? If you're using Trados SDL, Suzannah's steps should help. You'll want to export your file from Trados again, and then upload the new file to your Rise 360 course to restore missing text and get rid of the [object Object] tags.

If not, please feel free to work directly with us here!