Downloading Xliff files in Rise - different output

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.

Ok my quick workaround is using the following site http://www.beyondf.com/tranzapp/translate/

but I have to change my rise translation output .Ext from .XLF to.XLIFF by renaming it on my computer, then when I have made my text changes/translations, I export from the site and change the ext back to XLF, this seems to be working, but its a bit of a hack.

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!    

Hi everyone:

I encountered the same issues and found the following workaround:

1. Duplicate the course.
2. Export the 'xliff' file (which is really a .xlf file)
3. Add .xliff to the exported .xlf file
4. Upload this .xliff file to http://www.beyondf.com/tranzapp/translate/ and download the file (in Internet Explorer, In Chrome the 'Download' button does not work!)
5. In Chrome, import this converted file into the original course (NOT the duplication)
6. Follow the same process for any other translation; the original course is now translated into another language, but it still needs to be THAT original file/course.

Hi Valeria, 

The recent fixes released to Rise for XLIFF files did change the file extension to end in XLF, but those two file types should be interchangeable (similar to a JPG and JPEG). 

If you've run into trouble with the translation files after the latest update, I'd like to get copies into the hands of my Support Team to test.

Can you share the following with me here or click here to start a case:

1. The .xlf you've exported.
2. The .xlf you are trying to import.
3. Information on the tool (if any) you are using for translation.

Thanks in advance for sharing those, and we'll get you back up and running as soon as possible! 

Hello Ashley and Valeria,

We are also experiencing problems with the new format that Rises exports. There are several changes in the xml (for example, the html tags are replaced by <g> placeholders) that are not compatible with the programs we use to translate. The new format does not seem to works in the free editor that you recommended in the previous version of Rise (http://xliff.brightec.co.uk/).
Please, can you keep the previous version? It is very important for us, we think that it is a mistake to implement such big changes without warning, we have a project stopped due to this.

Thanks in advance!

Regards, 

Diego from G.A.

Hi all,

Same here. We are trying to translate a Rise presentation but the exported xlf does not work in our workflow anymore and when we try to import the translated xlf the tool says it is not recognised because it's not an XLIFF file. How can we solve this, please?

Thanks!

Hello everybody,

we have a similar problem. Since last week our translation office can not Import our XLF files any more. The issue is that the XML code structure has changed. Until last week it contained lines of the source language + the same content again for the target langue. The two were of course identical as the target language needed to be translated.

Here an example:

<source>CN Sales Tools and Platforms </source>
<target>CN Sales Tools and Platforms </target>

That's how the structure of the XLIFF files looked like until last week.

The new XLF file doesn't contain any lines for the target language anymore.

We also had to stop current translation projects with our translation office (they use Trados) like Diego mentions above. It might work with new projects (we haven't tested yet), but we can not continue  with ongoing projects for which our translation office has already received a XLIFF file and is now getting xlf-files (with updated content and a new XML structure).

Please let us know a possible bi-pass. It's pretty urgent.

Thanks & regards,

Eckart / Germany

Hello again,

I just had our translation office on the phone. They work with Trados, version 17. They confirmed that they can import the new xlf-format. The only problem they are still facing is to match an already translated XLIFF file with updated content that we provided with the new XLF format. Due to the new XML structure their translation memory system doesn't recognise already translated content as a 100%-hit. Trados thinks that it's new content or marks known phrases as only 50%-hits.

In short: in our case the new XLF format will work for future Rise translation projects. For current projects we have to pay the translation twice.

Eckart / Germany

Ok, so this is not helpful, there seem to be sections of text missing Paragraph blocks in general, when I view it at http://xliff.brightec.co.uk/, 

This was working before when this output was the xliff.

I have been working on a project for six months and in December I am due to begin translations into 5 other languages, so this is a big problem for me.