Downloading Xliff files in Rise - different output
Nov 01, 2018
Hello everyone, I am facing some issues exporting the XLIFF files from our courses in Articulate Rise.
I previously downloaded the same courses in the XLIFF format, however now I get xlf files with the internalised html and the file original code missing. The segmentation in the new downloaded file is also very different and poor.
As we already prepared these courses for translation and they are currently with the linguists, it would be quite problematic if we need to reprepare everything from scratch.
Is there a way to download the same format as before? What is this issue due to?
Thanks!
Valeria
76 Replies
When you read my comments above, you will see that we struggled with the same problems as you did. For a couple weeks we used the workaround via byondf.com that Craig Sumner mentions above (thanks a lot for sharing that with us, Craig!).
Today the big surprise: I imported a translated xlif-file and -- no error message, just an "OK"!! I didn't use any workaround. I just imported the file how I got it from our translation Office (the file came from the same translation office as in the past).
Maybe Articulate has fixed the problem? Has anybody of you tested an import during the past 24 hours? On my side it worked perfect today.
Eckart
I am seeing if our translation company can test this out by modifying my output so I can see what happens when I re-import it.
Will post back when I have done so.
Hi all,
Is anyone still feeling stuck here? Please reach out and we'd be happy to help! You can also submit a case to our support team.
Any updates with this?
Thanks for reaching out, Aaron!
I don’t currently have any updates, but you are now subscribed to this conversation which means as we share updates here, you’ll automatically be notified.
Problem seems to be solved.
Also the last XLIFF-import that we got from our translation office worked fine.
I'm glad to hear that, Eckart! Thanks for sharing
Hi,
In my case I just received a translated xliff and I cannot import it in the course. Any ideas, please? Is there anything we need to do in the xliff before trying to import it?
http://www.beyondf.com/tranzapp/translate/ check it works in here first?
Also specifically what does Rise say when you try to import, and have you checked your course to see if it actually has imported
Hi Craig,
What exactly does that? Is it only for translation? Thanks!
If your file opens in http://www.beyondf.com/tranzapp/translate/ and you can read the translations then the file is working and I would say there is an issue with Rise, if it does not open in http://www.beyondf.com/tranzapp/translate/ then the file has possibly been outputted incorrectly.
You could try renaming the file ext also.
To do this I would make a copy of the file you have, rename the copy and where it says .xliff change it too .xlf and try importing into Rise again, I am not saying it will work but try it, this a solution I have read others use and which worked for me once or twice.
Hi Elisa,
Sorry you're having issues here! Did you follow these translation instructions? What's happening when you try to import it?
I can also add that we are running into the same kind of issues highlighted on this feed.
Anybody from Articulate who can give us an update whether the issue is going to be fixed any time soon?
Best
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.
You'll hear directly from our team today.
The support of articulate has been super swift in getting in touch with us so that we solved the problems within a few working days!
Great service and full support.
We appreciate!
I'm so glad to hear that, Marco! :)
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:
I encountered the same issues and found the following workaround:
Thanks, @Haneke!
But, as far as I can see, there would be no way to translate everything automatically.
That is one of our main concerns, since segmentation changed when they decided to migrate from .xliff into .xlf, and we had to face many fuzzies for files that were already translated.
Regarding Tranzapp, thanks for the link. I was not aware of that tool. Is there any way to add TMs/automatically propagate the translations when there are repetitions?
Regards,
David
Hi David:
Our course was translated by a translation company, so not automatically. My problem was to import the .xlf file we received from the translation company back into the course.
I am sorry I can't give you an answer.....
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.
Hi Allison,
we still have the problem, that the export file is NOT an XLIFF file like you write in all your descriptions. It is XLF which is can not be read by major translation tools and software.
Can you please export the files in XLIFF.
Hi, Bettina! The preferred file extension for XLIFF files is
.xlf
. They're one and the same.Is there a particular tool or vendor you're using that has trouble reading the exported file? Thanks!
Does not work for us either. Anyone find any other solutions?