Forum Discussion
Downloading Xliff files in Rise - different output
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
Hi Craig,
your workaround with byondf.com worked well. Thank you for that post! When importing the xlf-file I still got the well-known error message, but the import worked (it took me another 3-4 imports until I realized that I had to ignore the error message).
Eckart
as I said just rename the file ext from .xlf to xliff and that will stop error displaying, then just rename it back when you export from byondf.com
I could not get the translated file from BeyondF to import back into Rise. I did change file extension to .xlf before importing. What did you mean @Eckart Fischer "It took me another 3-4 imports until I realized that I had to ignore the error message"
Hello Lärbyrån,
concerning your question what I meant with "It took me another 3-4 imports until I realized that I had to ignore the error message".
The issue was that I changed the file extension to .xlf before importing the translated file back into Rise. The problem was that Rise displayed an error message that it couldn't read the import file. I tried it various times, but the message came back again and again.
The funny thing was that finally I checked the content of the Rise course and I realized that the translation was there!
My message is therefore:
Even though Rise might display an error message when trying to import a translation file, check the content of your Rise course. I my case Rise imported the translation in the background while displaying an error message that it couldn't read the import file.It's like the fuel gauge of your car says that the tank is empty - but it's full.
You may need to copy the first line in the original file overtop of the new file as it does change elements of the XLF here
also have you tried not changing the ext back? Rise still lets you import xliff
It actually worked if I did not change the file ending back to .xlf when exporting from BeyondF. That's strange. If I find out any more I will post i it here, thank you for this.
I can concur with these other folks - our translation project was moving along swimmingly until one day when I exported a file in XLF and it did not work for my translation anymore.
It seems that Articulate has no intention of dealing with this unpleasant situation :(
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.
