Forum Discussion
Rise 360 XLIFF Translation import success but content still in original english
I am trying to create a translated version of a Rise360 course. I've
1. Created a duplicate of the original English version
2. Exported the an xliff file from the duplicate and created a translated version.
3. Imported the the translated xliff file and received an message indicating the import was successful.
However, the content of the duplicate course remained in English. How do I get get Rise 360 to render the translations?
Hi Patrick! Thanks for reaching out! I see you've opened up a private support ticket with us.
We can continue assisting you there, so please stay tuned for an email from your inbox from us! Please makes sure you can receive emails from `@articulate.com`Hi Renz,
I too have had this issue crop up on 3x Rise courses - how best do I resolve this with you please?
Kind regards,Holly
Hi Renz,
I have the same issue. I already opened a case and spoke with a member of your team, but I couldn't translate the course yet.
Anyway, I understand where the problem lies. The thing is that my original course is in spanish, and I need to translate it to catalan. The code of the xliff file should be ES, but instead when I download it, the code is ENG-US. This is causing troubles when translating and inserting the new file in RISE.
So my question is if there is any way to change this original file code from ENG-US to ES?
Thanks in advance!
Hi, Anthesis! There isn't a way to set the language code in Rise at the moment. Thanks for letting us know you need this feature!
Hi Lea,
I understand that I can't change de langauge code, but what I don't understand is why the code is en-us if I have the original course in spanish and settings of RISE in spanish too.
Does the code always come out in en-us even if the course is in Spanish or is there a problem here?
Thanks for your help!
Hi Anthesis,
Have you tried this?
- Open your file in Notepad.
- Change the following line <file original="course" datatype="plaintext" source-language="en-US"> to <file original="course" datatype="plaintext" source-language="es"> (it will be near the top of the file.)
- Save the file and then open it in the application you were adding your translation in.
Note: If you import the file back into Rise and it's not showing the Catalan translation, check to see if you have <target> elements in the file. If you don't have these, Rise won't be able to see the translation and you will only see it in the <source> language.
Hi Thor,
I'm going to try this. Thanks for your help!!
That's right -- the source language code in the XLIFF file will always be source-language="en-US" even if you created the course in another language.
If you're still having trouble seeing the translated content in your course, please let us know. I see that you mentioned you opened a case already, but I wasn't able to locate it by doing a search with your email address. If you can share your case number with me, I'd love to have a look at how our team has helped you so far.
Hi Alyssa,
I have two case numbers: #03155456 and Case #03152831
Yes, I'm still having trouble with it, so if you can help me it would be great!
Thanks,
Thanks for letting me know! I see you were most recently working with my teammate, Fannie, so I'll ask her to reach back out to you!
I am also having this issue and have tried everything listed above. Very frustrating, trying to get his course out of the door for our Japanese customers. Any help is appreciated. I will open a case.
For anyone googling this in the future, the imported XLIFF was missing the target-language="ja-JP" attribute & value for our Japanese course. The target-language attribute was not part of the XLIFF export from Rise. Seems like it should be.... I posted this: https://community.articulate.com/discussions/rise-360/exported-xlif-does-not-contain-target-language-tag-translations-do-not-appear-after-successful-xliff-import
