I have just received the translated files (from English to Simplified Chinese) from the translation agency. Now, I have successfully imported the .xlif files into Rise, but I still continue to see the English version of the course whereas I am importing the Simplified Chinese version. Do you have any idea on the reason for this unexpected behaviour? How could I solve it?
In most cases, we've found that people run into this issue when they try to manually translate the XLIFF file instead of using translation software. I would reach out to your translation agency and make sure they're using translation software for their translations.
If they confirm that they did indeed use translation software, please reach out to our Support Team so they can take a look. You can submit a case here.
In the meantime, if there's anything else I can do to help, please let me know!
Hi, I have the same issue. The translation company has used the software 'MemoQ' to edit the translations. Has a universal solution for this been found as yet? I have opened a support case (# 01970148) but need to resolve asap to deliver the work today so any help here would be much appreciated.
Ok I worked out the issue (in my case). I had duplicated the original English course to create a French version and then imported the translated xlif. However, as that xlif originated from the original English course it didn't work. I therefore had to do a new export from the duplicated course, have that one translated and then re-import. Hope that helps someone...
I want to reply and say I have this bug to and might be opening a support ticket.
I work for a very large international localization company that specializes in eLearning. My office alone does many RISE courses each month.
Once and awhile, we get a file that says import was successful but it remains in English.
for example, I have a course in to 5 languages. 4 worked (imported) into their target courses fine fine, 1 did not. All were duplicated from the same master EN file at the same time. Labeled for their target languages, and then XLF created from each copy andthen translated (with CAT [computer aided translation] tools, not by hand).
The only fix I've found that works is to re-duplicated EN, make a new extract, re-clean (what we call moving translations from a Translation Memory into a target file) and import.
That has worked so far, but now I have one that no matter how many times we duplicate and re-prepare files, it never imports.
I see that you have a case with Robert about a Rise 360 translation issue, and he recently requested a copy of your course for testing. Since that's the best way for us to nail down the cause of the issue, would you mind sending your course our way?
In that case, we found that text in the XLF that did not appear in the course.
Upon closer inspection the text is the "dummy" text that is put in elements when you create them. My guess is that a box was created, then deleted, but the text remained in the database.
Even though the text does not appear in the course itself, our client ended up paying to translate words (a small amount) not needed and during client review the reviewer was confussed where that text was coming from. So that's the issue.
Thanks for clarifying that, Matt. That's definitely odd. I'll share this with our Rise product team so we can take a closer look at this behavior. If I get any updates, I'll pass them along to you!
Hi there, Matt. We want to try recreating this issue on our end, and we need a little more help from you. Specifically...
What web browser were you using to author the Rise 360 course?
Do you know which block type was deleted?
It's possible that the filler text came from a block type that can be converted to other blocks. For example, if you add a Paragraph with Heading block, then change it to a Paragraph block, the heading text is preserved in the background in case you want to switch it back.
If you know which block type caused the issue, that clue could help us nail down a solution!
This --> "In most cases, we've found that people run into this issue when they try to manually translate the XLIFF file instead of using translation software."<--Should be fixed to allow for translation via more common tool/output format. Other Articulate products have the option to handle translations EITHER as XLIFF OR a format that 99% of the population can access/edit, but NOT RISE. Although I do appreciate that RISE is unique, it sometimes makes the "things we thought we had figured out" more challenging.
I am having the same problem as others. I am testing out this process--I exported the course, then translated just a little bit of it and imported. The import is successful, yet the text in the course has not changed. This is really going to be a problem for me, as translating individual blocks is just what I had expected to avoid...
Thanks, Kristen. It sounds like you're doing everything correctly, so I'd like to connect you with our Support Engineers so they can look closer at what's causing the breakdown.
I've opened a case for you, and you'll hear from the team soon!
I don't do the "engineering" as we call it at my company on the xlf, but I know simply updating the English text isn't enough.
When you look at the XLF, you see tags on either end of each part.
In an XLF, immediately after, you put the translation you want for that inside tags.
Example:
This sentence is the English source content and stays in English
This is where the translated version of the source would go.
If you are doing that part correctly, then I would try making a copy of your course, exporting the XLF, and try again.
I am having the same problem - please can someone help me? I have done as the steps say and the import is succesful but it will not display. Please help urgently
I have the same problem. I have copied the file, received the translated files, they import but nothing changes. This a super urgent for me too. Please help. Tracy
32 Replies
Hi Alessio,
In most cases, we've found that people run into this issue when they try to manually translate the XLIFF file instead of using translation software. I would reach out to your translation agency and make sure they're using translation software for their translations.
If they confirm that they did indeed use translation software, please reach out to our Support Team so they can take a look. You can submit a case here.
In the meantime, if there's anything else I can do to help, please let me know!
Hi, I have the same issue. The translation company has used the software 'MemoQ' to edit the translations. Has a universal solution for this been found as yet? I have opened a support case (# 01970148) but need to resolve asap to deliver the work today so any help here would be much appreciated.
Ok I worked out the issue (in my case). I had duplicated the original English course to create a French version and then imported the translated xlif. However, as that xlif originated from the original English course it didn't work. I therefore had to do a new export from the duplicated course, have that one translated and then re-import. Hope that helps someone...
Perfect work, Lester. Thanks for clarifying and for letting us know in both the forum and your case. ☺️
To summarize, after duplicating your course, perform the export from the duplicate since you'll be importing the translation back into that version.
Let us know if you need anything else!
I want to reply and say I have this bug to and might be opening a support ticket.
I work for a very large international localization company that specializes in eLearning. My office alone does many RISE courses each month.
Once and awhile, we get a file that says import was successful but it remains in English.
for example, I have a course in to 5 languages. 4 worked (imported) into their target courses fine fine, 1 did not. All were duplicated from the same master EN file at the same time. Labeled for their target languages, and then XLF created from each copy andthen translated (with CAT [computer aided translation] tools, not by hand).
The only fix I've found that works is to re-duplicated EN, make a new extract, re-clean (what we call moving translations from a Translation Memory into a target file) and import.
That has worked so far, but now I have one that no matter how many times we duplicate and re-prepare files, it never imports.
Hi there, Matt!
I see that you have a case with Robert about a Rise 360 translation issue, and he recently requested a copy of your course for testing. Since that's the best way for us to nail down the cause of the issue, would you mind sending your course our way?
Let me know if you need any help with that!
We finally got it to import. So here's the thing.
Normally when this happens, we can make a copy of the EN (English) again, make a new XLFF, translate, and it will import.
This time, that didn't work. Multiple times.
But what did, was copying it to a different account all together, new XLFF, translate, and import worked.
I'd share it (after I get permission on this one as well), but you might not see the problem, since sharing it seems to fix the problem.
Thoughts?
Thanks for those troubleshooting notes, Matt. I'll add them to your case with Robert so we can continue to investigate what happened.
The case with Robert is different.
In that case, we found that text in the XLF that did not appear in the course.
Upon closer inspection the text is the "dummy" text that is put in elements when you create them. My guess is that a box was created, then deleted, but the text remained in the database.
Even though the text does not appear in the course itself, our client ended up paying to translate words (a small amount) not needed and during client review the reviewer was confussed where that text was coming from. So that's the issue.
Thanks for clarifying that, Matt. That's definitely odd. I'll share this with our Rise product team so we can take a closer look at this behavior. If I get any updates, I'll pass them along to you!
Hi there, Matt. We want to try recreating this issue on our end, and we need a little more help from you. Specifically...
It's possible that the filler text came from a block type that can be converted to other blocks. For example, if you add a Paragraph with Heading block, then change it to a Paragraph block, the heading text is preserved in the background in case you want to switch it back.
If you know which block type caused the issue, that clue could help us nail down a solution!
I don’t know what was used/done, as we translate courses for our clients, but the client is the one making them (in this case Stryker)
This makes sense. I’ll send it to the client so they know this. It’s possible that is what happened.
I don’t know what was used/done, as we translate courses for our clients, but the client is the one making them (in this case Stryker)
This makes sense. I’ll send it to the client so they know this. It’s possible that is what happened.
That sounds like a good plan, Matt. If you run into this problem again, we'd love to take a closer look at the XLIFF file itself.
You can send that file directly to our Support Team right here.
This --> "In most cases, we've found that people run into this issue when they try to manually translate the XLIFF file instead of using translation software."<--Should be fixed to allow for translation via more common tool/output format.
Other Articulate products have the option to handle translations EITHER as XLIFF OR a format that 99% of the population can access/edit, but NOT RISE. Although I do appreciate that RISE is unique, it sometimes makes the "things we thought we had figured out" more challenging.
Link to enhancement request please. -T
I am having the same problem as others. I am testing out this process--I exported the course, then translated just a little bit of it and imported. The import is successful, yet the text in the course has not changed. This is really going to be a problem for me, as translating individual blocks is just what I had expected to avoid...
Hi Kristen!
The first step in translating your course is to duplicate the course, then export the XLIFF from the duplicate.
Did you duplicate the course before exporting the XLIFF?
I have followed all of the steps in the guide to the letter.
Thanks, Kristen. It sounds like you're doing everything correctly, so I'd like to connect you with our Support Engineers so they can look closer at what's causing the breakdown.
I've opened a case for you, and you'll hear from the team soon!
Hi Kristen,
I don't do the "engineering" as we call it at my company on the xlf, but I know simply updating the English text isn't enough.
When you look at the XLF, you see tags on either end of each part.
In an XLF, immediately after, you put the translation you want for that inside tags.
Example:
This sentence is the English source content and stays in English
This is where the translated version of the source would go.
If you are doing that part correctly, then I would try making a copy of your course, exporting the XLF, and try again.
Best of luck!
This post was removed by the author
I am having the same problem - please can someone help me? I have done as the steps say and the import is succesful but it will not display. Please help urgently
Hi Emma!
Thank you for opening a case and including your XLIFF file for our team to test. I see you're already working with Vevette — you're in good hands!
Hello,
I have the same problem. I have copied the file, received the translated files, they import but nothing changes. This a super urgent for me too. Please help. Tracy
Hi Sina,
I am sorry you are experiencing this issue.
To confirm, you are importing the XLIFF file to the exact same course where it was originally exported from?
If you are doing exactly that, please open a case here so we can take a closer look.