Forum Discussion
NEW in Rise: Export for Translation
If you need to create courses in multiple languages, you’re going to love this new Rise feature. It allows you to export your course text to an XLIFF file* and then reimport it once it’s been translated. Like magic: all your text is replaced by the translated text. It’s that easy!
*XLIFF files are a translation industry standard, so if you’re working with professional translators, then you shouldn’t have any issues. But what if the translations are being done by a fellow coworker or friend? No problem! If you do a quick Google search, you’ll find a ton of free tools that allow you to easily edit XLIFF files.
- GrupoAssBiomediCommunity Member
Dear Rise staff,
Any news about the html tags problems reported?
Thanks!
Hello Grupo Asís Biomedia peeps! We are monitoring the impact of this issue and looking at our options, currently. Is your translation tool not able to use the Rise XLIFF files because of the tags?
- ElenaTagliatiCommunity Member
Hi, there is another issue. When the tags are in the middle of a word like apostrophe, the xliff comes out with ’ Of course the target language will have apostrophes in different positions. Does it mean that wherever they inserted an apostrophe in their translation they should replace it with ’ ? How would normal apostrophes appear when the xliff gets imported back into rise? Thanks
Hi Elena,
Thanks for reaching out to describe what you are seeing as well.
Are the HTML tags included in Rise's translation output is causing issues for your translation service or are you concerned that they might? We are still tracking reports and investigating issues.
Is your translation service unable to use the files at all? I'm curious if you are you are using Trados or another service?
Thanks for your help!
- ElenaTagliatiCommunity Member
Hi, they are using trados, i haven t imported the xliff back into Rise yet. The question was for the tags inside the text like apostrophes, as they obviously fall in different places than the original text in english.
For example, when the new sentence in french is "je suis d'accord", is it ok to write it like that, or they need to put "je suis d 《’》accord" instead?
If that has to be done everywhere there is an accent in french (and what about è,é,à, etc?) It becomes almost impossible to work with the xliff.
Thank you for your support on this issue!
Best regardsHi Elena. Thanks for elaborating. We are currently investigating what changes we can make to how Rise generates the XLIFF files. Trados is one of the tools we found to have an issue with the HTML tags that Rise includes.
At this time, Rise keeps those tags because text in Rise starts as an HTML field, and it wants to keep as much formatting as possible in the translation process. Not all translation tools are handling the resulting XLIFF. I understand this is an issue for you and other folks, so we're making sure we're prioritizing it correctly!
- JennaGallagh447Community Member
Hi there.. is anyone else having issues with the text changing after importing the new language? For example, in Polish we are seeing a lot of randomly bold characters. We also noticed that the label imports for Chinese didn't work.
Hi Jenna,
I haven't seen text appear bold after translation, was this on the entire course or just the labels?
Also, for your Chinese labels, it sounds like they didn't update or did something else happen like the text appeared oddly? If you could share some screenshots or more detail about the steps you went through that'll help us track it down.
- JennaGallagh447Community Member
Hi Ashley,
This feedback came from the vendor we use for localization. For the Chinese labels I know they weren't able to import without receiving an error. I'll see if I can get them to join the conversation. Thanks!
- KennethFarrallCommunity Member
Hi Ashley,
I'm employed at the vendor that was on this project and I can add a bit more information on the problem. For the Chinese label issue, I was trying to upload a translated XLIFF file for Chinese labels and got the following error message: "Error: Incompatible format." We uploaded similar XLIFF label files for Polish and Portuguese without any issue.
For the Polish, it's a problem we have also seen in Storyline 360. In the case with Rise, it happened when special formatting was used, such as for a quote. I have attached an example. Changing the special formatting from Statement C to Statement D fixed this issue. There were 3 or 4 instances of characters being individually bolded throughout the course.
Hi Kenneth,
Thanks for sharing some more details. What translation tool were you using for the Chinese Labels? We've heard some similar issues using SDL Trados Studio 2017 and MemoQ.
For the bold fonts, it seems from that image it's only on the special characters? Were you applying special formatting, or relying on what Rise adds based on the block type? When you've seen the same thing in Storyline, what format was applied there? I'm glad switching the statement type fixed this, but I'll take a look at the statement C setup too.
- KennethFarrallCommunity Member
Hi Ashley,
For the Chinese labels we were indeed using SDL Studio 2017. Studio and MemoQ are market leaders in the CAT tool space.
Regarding the bold fonts, we did not add any special formatting. I also noticed that the bolding appears on some, but not all, special characters. The problem we encountered in Storyline also occurred in blocks of text without special formatting. In addition to being bolded, characters appeared as different sized fonts in the same word. The problem in Storyline was intermittent and not always reproducible. Our experience there was that files might look fine on our side, but if another person opened the same file they might encounter these issues, or we might encounter them after executing an import of translated content.
I have added two additional examples of the Polish bolding in Rise. Example 2 uses the Quote B style. Example 3 is a little different, in that case, it seems that the Rise display system is not properly reading the close font tag. Bolding should end where the comma is in the first sentence, but it just continues to the end.
Thanks, Kenneth.
I know our team is looking into the issues with SDL Studio 2017, so I'll keep you posted on that here.
Thanks for the images in Rise too, I tested out myself with some random Polish text (courtesy of Google Translate!) and I didn't see bold text, but the accented characters were actually quite smaller. Can you let me know what font you're using in Rise? I'll share both examples with my team so that they can take a better look!
- KennethFarrallCommunity Member
Sorry for the delay in reply, Ashley,
It looks like Merriweather is the body font on this module. Lato is the headings font.
Best,
Ken
Hi Kenneth,
Have you already looked into the steps here to resolve the odd character issues?