41 Replies
Crystal Horn

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!

Lloyd Hill

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.

Gustaf Sylvin

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

Allison LaMotte

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. :)

 

andrew donald

Good to know as we've had similar issues exporting from Rise. 
Storyline exported content including coding to Word, very easy for translators to use and for us to import back into SL. Translations using Rise appear to be highly manual as stated above.

With Rise, the only option when exporting for Translation is XLIFF, which is problematic for L&D as well as Translation Team.

Irina Poloubessov

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.

 

 

Irina Poloubessov

Dear Crystal,

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.

 

Alyssa Gomez

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.

Julie Pochik

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 :-(

Claudia Di Lorenzo
Julie Pochik

Please can someone help us.... I really need translation for RISE and Smartcat is not working for me everything is manual... Please someone help. Storyline is so much easier into the word file as stated above.

Hi Julie,

Did you find a solution for this? I can help by asking a professional translator to take care of the translation if you wish. What language do you need it translated in?