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
- CraigSumner-890Community Member
also have you tried not changing the ext back? Rise still lets you import xliff
- StefanSj-a62f91Community Member
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.
- AdriaanVanNieuwCommunity Member
This is the error that is being presented and it appears to be with newly created files:
Stacktrace:
2018-11-26 09:58:39 XML file error - org.xml.sax.SAXParseException: The reference to entity "d" must end with the ';' delimiter.
- IvorThynne-1cb6Community Member
Hi Ashley,
I am having the same issues as Adriaan, our files are just not uploading I am not even able to import the original file back into the course!
I have two other courses that were originally built before or on the 1st Nov which I am able to import the original text files back in (however text edited using notepad ++ does not seem to copy over).
I am talking to your colleague Chris regarding this, he has taken and shared a peak video of it working and updating correctly but as I am not the only one with issues, I really do not believe it is just me doing something wrong.
Please can someone look into this overall and help us all out.
I have already spent out £2k to update my Translation memories without the new courses just about to be started and it looks like it still will not work!
HELP!
- RebeccaMogol421Community Member
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.
- GrupoAssBiomediCommunity Member
It seems that Articulate has no intention of dealing with this unpleasant situation :(
- EckartFischerCommunity Member
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
- CraigSumner-890Community Member
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.
- AaronWeislog524Community Member
Any updates with this?