Forum Discussion
Translation of Rise Course
Has anyone used a translation vendor that can translate directly from Rise? I don't want to have to copy and paste an entire rise course into a text editor just to get the text translated. Suggestions appreciated.
Hi Zuzka,
With Rise we added XLIFF translation as it's an industry standard for localization, and there are many free and premium tools for working with XLIFF files (Here’s an example of a free web editor for XLIFF files.) What type of formatting issues have you run into? Rise uses XLIFF version 1.2, do you know what version your translator was using?
Dear Ashley,
Rise translation does not work with Trados 2017, which is still a software use: it destroys the text by import with inserting [object] tags.
I contacted the support and got a reply:"the issue is rooted from the inclusion of </g> tags from the exported XLIFF file which doesn't work well for specific translation tools.
We included this tag to make sure the texts in the course don't lose formatting when translated. The </g> tags essentially keep the format of the texts such as bold, italicized, etc.
Additional info:
a. By definition, it is a tag for SVG element which is a container used to group other SVG elements.
b. Transformations applied to the <g> element are performed on all of its child elements, and its child elements inherit any of its attributes.
c. Translating documents with <g> tags may not be continuous since some texts may have different formatting in one paragraph.
To exclude the </g> tags from Rise' exported XLIFF, you can opt to disable the option "Include HTML formatting"."
We cannot exclude the HTML formatting as it would result for a big manual labor and time loss when manually returning back all lost words in bold, colored headers, etc.
Please allow exporting from Rise in Word format exactly like from the Storyline (which works great), if it is not possible to produce manual-labor-free translation with XLIFF.
Hey everyone! I’m happy to let you know that we just made translating content in Rise even better. You can check out the release notes here.
We fixed an issue where XLIFF translation contained HTML tags that some translation tools couldn't process.
The new version of Rise is live now, so just simply export your XLIFF translation again and let us know how your tool handles it!
The XLF editing tool Articulate has recommended in several posts is http://xliff.brightec.co.uk/. When attempting to translate files using this tool, the following does not render the original text:
<trans-unit id="description">
<source>
<g id="9VrwBi4Ofg0tBfvB" ctype="x-html-p">Some text</g>
</source>
</trans-unit>What does work is manually removing the g tag:
<trans-unit id="description">
<source>
Some text
</source>
</trans-unit>So this editor is pretty useless, as almost ALL original text is not displaying.
Hi Lloyd,
Sorry that you’ve hit a roadblock here. We’re actually recommending SmartCat now. We’ve found that’s working better for folks. Bonus: it’s free!
Give that a try and let me know if I can be of anymore help.
Hi.
I exported my translated labels and tried to re-import them. Then all custom fields says Add a label. I have opened the XLIFF files and it contains all translated words. What goes wrong in the import?
Another question too; if I make a template to send to my project group with translated labels, will the they be able to see the translation? My experience is that the translation is lost when sharing a course.
br
Gustaf
Hi Gustaf,
It's hard to say what could be going wrong without having a look at your file. The quickest way to resolve this issue is to have our Support Team take a look. You can submit a case here.
To answer your second question, when you send a copy of a course, it uses the recipient’s default English text labels. If you'd like, you can export your custom labels to share as well. Here's how to do that.
Let me know if there's anything else I can do to help. :)
Hi Irina!
Thanks for working with Renson and Vic in your case. Vic recently sent you an update, and I'll share it here for anyone else using Trados 2017 or Trados 2019.
Our team ran further tests using Trados 2017 and Trados 2019, and we confirmed that the option Do not store segmentation information in the translated file is available in both versions of Trados Studio.
To summarize, if you're having trouble translating a Rise XLIFF file in Trados Studio, enable the option Do not store segmentation information in the translated file in both areas of Trados Studio. Here's how:
- File > Options > XLIFF > Settings > Do not store segmentation information in the translated file
- Project Settings > File Types > XLIFF > Settings > Do not store segmentation information in the translated file
Doing this will ensure the <seg-source> tags are not included in the file, and you can import it into your Rise 360 course without any issues.
If you need a hand with either of those steps, our Support Team is here to help.
Dear Alyssa,
Thank you very much, I will try it out and let you know if it worked.
Hi Alyssa,
I realise that this is an old thread, but we are experiencing the same problem at the moment and trying to understand the implications. We are working with an external translation company that is using Trados (not sure what version), and the XLIFF file that they have sent us displays empty text blocks after import. The code does include <seg-source> tags, can I assume from the above that these are not compatible with Rise360? The follow-up question is if we remove them, will this affect the formatting or display of HTML content such as tables etc?
Cathy Evans
Hello Cathy,
Sorry for the trouble with the translation. We'd like to take a closer look at the XLIFF file to make a better recommendation. Would you be willing to share it privately in a support case? We'll reach out soon after we hear from you!
I tried using Smartcat and upload my translation file back to RISE. I can see the translation on the right side of the Smartcat doc and worked with a rep from Articulate he told me the file did not translate into the target area in Smartcat. I have tried multiple times to contact Smartcat with no luck. Does anyone know how to do this? Or do I have to pay for a service. HELP :-(
Can anyone give me a time estimate for the admin for translating a course? How long does it take to get export the file and once you get the translation back from the translators to get the course ready?
The XLIFF file format from a quick looks requires each field to be copied and pasted. Is this correct? This seems really time consuming.
Do any companies out there offer this whole service?
We are trying to work out the cost for selling a translated version of our courses.
Can anyone help me?
I am in the same boat as you.... Everything is manual. I just sent a note to Articulate asking the same thing and for help... Why can't it be a word file like Storyline?
Hello Kirsten,
I can help with the translation of the XLIFF file without any problem. Would it be possible for you to send me the file via email? I will then be able to send you an exact quote (based on language and volume) and turnaround time for us to complete the task!
My email is claudia@translated.com. Feel free to reach out.
Hey Julie,
I see your case with Richard, and I'm sorry this has been a frustrating process for you! Please let us know if you have any questions about what Richard shared or if you need help with next steps. We're here to lend a hand!
Hi all,
I am wondering about everyone's experience when importing translated text back into their Rise course.
The xlf that I am working with is 91 KB, but it seems to get stuck at the Processing Translation stage.
Hello, James! Let's address a couple of quick ideas to see if we can get you moving forward:
- Make sure the XLF came from the same course copy from which it was exported.
- Close the course or refresh your browser, and try the import again.
If that doesn't help, we're ready to have a closer look with you.
Thanks Crystal,
I solved the issue when I made two changes; I am not sure which fixed it.
- I was trying to upload the file into a duplicate of the course, which had the word "Copy of" added to the normal name of the original, so I changed the name back to the original.
- I changed the file extension to xliff - I was using the .xlf orginally
Either way, all good now!
