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.
183 Replies
Am I the only one who feels that the bugs and problems reported on this forum systematically seem to be answered by bots? Always the same answer "we will forward to our support", under the understanding that with a little luck a member of the community will bring free solutions. Hey Articulate, your product is a commercial product that you sell expensive, your customers are entitled to get concrete answers to the problems that your product imposes on them. A bug is not a request for functionality to prioritize according to your development backlogs, they are problems to solve all the more quickly as they are blocking for YOUR CLIENTS!!!! The problem described above by Julien has been lying around for months on your forum and has still not been solved. It involves very high manual intervention costs, and for any answer Articulate answers "we are looking into it"??? It's not serious and personally I wonder if we can really continue to recommend Articulate to our customers. Other solutions exist on the market and offer serious support. It would be time for Articulate to rebalance their staff between marketing and developers. The latter must not be very numerous....
BR
a customer for many years but who is at the end of his patienceHi Sven,
No you are not the only one. The issues that Articulate have introduced with the supposed improvement to the translation feature have resulted in a massive amount of manual work for us and a huge translation bill due to previously built-up translation memory being more or less rendered useless.
We've had to give up on the translation feature and gone back to manually duplicating the courses and applying translation section by section.
We are already now looking to move away from Articulate altogether which is a real shame as we've invested a lot of time into the products over the years but the recent issues seem to suggest that they are completely detached from the pressures being experienced in the field.
Thanks,
Matt
Matt, Sven, all: I had a call with Julien (from above) and I'm already helping him fix his files. We will soon be helping Articulate fix these issues as well. They are not a problem that is difficult to solve for us.
Book some time with me today or Monday and I'll troubleshoot any issues you have, or get you prepared for your next translation.
Best regards,
Jeff Weiser
Account Executive - Americas
+1.857.326.5868
smartcat.aiThank you for your proposal, Articulate should, again, enjoy the fact that they can thus escape their duty to solve the problem... But it's not a solution for us. We have projects in between 10 and 20 languages each, with hundreds of files to process. I don't want to be dependent on a third party service, we paid Articulate to have a product that works!
BRHi, I am using a trial version of Rise and intended to purchase. However, this "easy translation" feature that was of great appeal to us seems to be flawed and buggy, requiring a third-party to help resolve. Before sending a .xlf file to translators, I tested an output, then direct import (no changes to the file) and received the same error message as above. Obviously, there is an issue on the Rise side.
Hi Raymond,
I'm sorry you ran into issues with the translation feature during your free trial. I went ahead and submitted a support case on your behalf. Our support team will be in touch with you shortly to help you get to the bottom of this.
In the meantime, if there's anything else I can do to help, please let me know!
Hello, everyone.
Thanks for weighing in to let us know how important it is for us to get XLIFF translation right in Rise. We hear you, and we understand this is impacting you. Our team will be reaching out to each of you directly to schedule some focused time to get your feedback on the best way to fix this.
Just one clarification here - Jeff is not working with our team on this. I want to be clear in case folks think he’s acting on behalf of Articulate.
You'll hear directly from our team today.
Hi.
We're experiencing a problem with Russian/Cyrillic font. We've successfully imported the Russian translation of a course - but the font is not shown right.
We've followed all the steps in the guidelines (i.e. created a new custom font that includes Cyrillic, and Cyrillic Extended, had this transformed into .woff and imported to Rise.) We called the new font set 'Roboto Cyrillic' - but it doesn't make any difference to the appearance of the text whether we choose this or any other font.
Should/could something be changed in the .xlf-file ? - or elsewhere?
Thanks.
Hi, Louise! I'm sorry that you're having trouble getting your fonts to display properly. It sounds like you might have already done this, but I wanted to make sure you've downloaded the full Google Font set for your Rise 360 fonts as detailed in this article.
If you've already completed those steps and see the same results, then the quickest way to resolve this issue is to have our Support Team take a look. Please submit a case here, and we'll get you back on track.
I can't understand why you don't restore previous option to export and import .xliff while you solve current problems. There was a functional feature, it was already done and working, you only have t restore it… could you ask to do it, please?
Thank you.
Hi everyone,
Some of you have told us that the tags we add to XLIFF exports (to preserve formatting) make those files hard to work with.
If you’re one of those people, I’ve got some great news! You now have the option to discard that formatting in order to make XLIFF files easier to work with. Here’s more information on how that works.
Keep in mind that if you decide not to include these HTML tags, any custom text formatting (size, color, boldness, etc.) that you’ve applied will be lost when you import your translation.
We've also reduced extra spaces in the export files so that they work better with third-party translators.
We’re hoping that these changes will relieve the pain that some of you have been experiencing with translation in Rise.
Thanks for your patience as we worked on this solution!
Let me know if you have any questions.
Dear Allison,
Thank you for the update.
Does this mean that the bug which was inserting [object] tag and erasing some of the text when importing the translation (Trados 2017) was resolved? Support Case #01575929
Hi Irina,
You now have the option to disable formatting when you export for translation. I would start by trying that out and seeing how that works with Trados. If that doesn't fix the problem you're having, I would try using the instructions provided in the Trados community.
If neither of these solutions work, please let me know and I'll have our support team reach out to you.
Hi there, I have some problems with the translation of a course. I have imported the .xlf file and it seems to go successfull but... it doesn't change anything. Is there something I missed?
Please help me! See the scrinshot here. I don't know what else to do!!!
Hi Enrico,
Did you use a translation tool to edit the .xlf file? Or did you try to edit it manually?
In most cases we've found that people run into this issue when they try to manually translate the XLIFF file instead of using translation software. XLIFF files are complex and often when people try to manually translate them, they don't replace the necessary text in order for the translation to import correctly. If you've tried to translate the course manually, that's likely what's going on here.
If you used translation software, please reach out to our Support Team so they can take a look. You can submit a case here.
In the meantime, if there's anything else I can do to help, please let me know!
Thank you Allison! We have fixed the problem. It was maybe a codification problem due to some strange characters we used. Thank you so much for your quick answer! :)
Phewf! I'm glad to hear that :) You're welcome
Hi,
we would like to export as a word document like storyline does. In our company we are not allowed to use free software and most software is not allowed to be installed in our system, We have a lot of restrictions here. Are you considering to implement a word export too?
Regards
Susi
