Rise Translation Import Stuck in Processing

Hi, I have the same issue here. It can't be because of the file I'm importing, as I've used it before.

Hi,

I have a the same problem with one xlf file (in Russian).

I've duplicated my course, I've exported the course as an XLIFF File, I've imported XLIFF File traslated with Trados, but at this last step, xlf file gets stuck loading. It does not give an error, it just gets stuck loading.

I've changed the font (I've import a russian font).

I've imported also labels traslated, and they work.

The problem arose only for xlf course.

I am also unable to import translations after following the correct export process. I submitted a ticket.

Hi,

When a collaborator sends me a copy of a course, can I import that translated text to the copy I was sent?

Colleague created a copy of a course then exported the xlf file for translation.
I now have taken over the work, sent xlf file it to a translation company.
Colleague sent me a copy of the course (now showing my name as the author).

I have been trying to import the translated xlf file but stuck in processing.

Does my colleague need to import the translated xlf file himself on the copy of the original course where he exported this file?

Question 1:  Different author cannot import translated text to a copy of a course that another author sent them?

OR....  Sending a copy of a course changes the fingerprint of the course so the imported file can only be done by the original author of the course?

Does sending a copy of a course change the fingerprint?

Hello 
I would like to ask for a support with the same issue as reported multiple times in this thread.
My issue is regarding one of the modules where translated xliff doesn’t work in each of the 6 language versions i have. All of the correct steps were followed so:
1.Export the XLIFF file from your copy
2.Translate that XLIFF file
3.Import the new translation file into your copy of the course.
I've also tried re-exporting the xliff again and sending the file to our team responsible for translation to process it again. Unfortunately this fix didn’t work as well. 
Is it possible that the Rise file created/duplicated from the original English version is bugged or the source file which I’m duplicating? I would appreciate your help and some guidance to try and resolve this issue.

I'm having the same issue. My file is stuck on "Processing translation" with a spinning wheel. I am only using one file and one translation. 

Here are some ideas that may help you get through this issue. If you followed the correct export and import procedure, then the issue may be caused by some tags in the XLF file that was exported from Rise or Storyline. 

Thousands of tags are generated by Storyline, and Articulate doesn't always tell us where or what tags are causing the issue during import. If we knew which lines in the translated XLF file had errors, it'd be easy to fix, instead of trying to find a needle in a haystack. 

Articulate does sometimes provide an error message when importing a translated XLF file, telling us which tag is causing the problem. eg. "A SpanningCodeStart with id span_3 was not found." (See screen shot.) This is helpful, but still requires a tedious process to locate the error. And there may be more errors! 

Sometimes the file just crashes or hangs during import, without any error message. However, you may notice that PART of the foreign language has imported. If this is the case, identify the slide in the training where it stopped importing the translation. Then I start by opening the translated DOCX file that we received from our vendor. Locate the corresponding place in the translated DOCX and XLF where a tag problem exists.  Remove extra tags that are out of sequence, or in middle of a sentence. You may see a word outside of the tags (between tags 4 and 5) or spacing is different (before rather than after the tag). Try to import again after saving XLF file. 

Another solution that may enable a successful import: Text that is copy-pasted from MS Word adds a lot of formatting tags that aren't necessary. So if you normally copy text into Articulate from a Word doc, consider copying into Notepad or similar first. I have not tried this as it will remove ALL formatting. 

FYI, I asked Articulate in a previous trouble ticket if they can update their software to always deliver an error message that includes the specific tag that is preventing the successful import, instead of just crashing or hanging. 

ARTICULATE, would a formal Feature Request lead to that outcome? 

I did receive this tip from Articulate:

There's no feature in Storyline that analyzes translation files, so I've used a third-party tool, WinMerge, to compare the affected translation file and the original text from the course. It looks like there are additional tags in your translation file. It can help identify tags present in your translation file that were not exported in the original text.

This is a long-winded explanation that (hopefully) lead to successful imports. Thanks. -Jill

Don't know if it will be any help, but much like a comment made up the page I finally got it to work. It wouldn't translate the duplicate but it worked straight away when I translated the original module. Not sure how that will help when translating multiple languages of the same module, but if it's just x1 language, use the duplicate as your English version (or base language) and use the original as your translated version. Hope that works for anyone