Hi Greta Magyar

Could you attach a sample file?

Daniel

Hi Daniel Hug

Sorry for the delay.

Please find below for download a sample file translated by Lokalise (EN-US) and the same file translated in Studio. Easygenerator accepts the first one by Lokalise, but not the one by Studio.
https://we.tl/t-FCqgbHq0NF 

Thank you for your help!

Hi Greta Magyar

I am astonished how different the two files are. The file produced by Lokalise is not bilingual - it does not contain the source language! Language codes in the header are different. Lokalise file target element does not have attributes. This might take a while to get right by trial and error - especially if only the customer can upload and report back to you!

Did you try asking Easygenerator's help about their Xliff import requirements?

Daniel

Thanks ... I downloaded the files last night and was going to investigate today.  But now I simply have no comment!

Greta Magyar do you have the original source file that was sent for translation?  It would be interesting to see what that looked like to guess how the target files wound up the way they have.

Thank you both Daniel Hug and

Here is the source file:
https://we.tl/t-E1xv0w05Mm 

This is the only info they share on their website on XLIFFs:

https://help.easygenerator.com/en/articles/2929564-xliff-translate-your-courses-into-multiple-languages-using-xliff-1-2-export-and-import?_ga=2.84616926.672950572.1602603808-147157572.1601651703 

I have not asked them yet, I just have seen the response they gave to the customer when they pointed out that they system is not accepting files translated by Studio, and they said it's because SDL is using the wrong XLIFF version / schema.

This is all I have at the moment, but happy to ask for more info.

Thank you both Daniel Hug and

Here is the source file:
https://we.tl/t-E1xv0w05Mm 

This is the only info they share on their website on XLIFFs:

https://help.easygenerator.com/en/articles/2929564-xliff-translate-your-courses-into-multiple-languages-using-xliff-1-2-export-and-import?_ga=2.84616926.672950572.1602603808-147157572.1601651703 

I have not asked them yet, I just have seen the response they gave to the customer when they pointed out that they system is not accepting files translated by Studio, and they said it's because SDL is using the wrong XLIFF version / schema.

This is all I have at the moment, but happy to ask for more info.

Greta Magyar

Greta Magyar said:

they said it's because SDL is using the wrong XLIFF version / schema.

What schema do they think we should be using?  I'd be very interested to hear the response to that.

The Lokalise file is nonsense in terms of what you would normally expect to see returned.  As Daniel said, the source has been stripped out altogether.  So if they require a specific format back, and perhaps that's what they mean by wrong schema, then it would be good to know what that should look like.

I ran a diff report on this and the only difference is that the Studio XLF now has a target translation.  For example:

The same comparison with the Lokalise XLF and its full of changes, even the header!

In my opinion Easygenerator are not using XLIFF as intended and the import format seems to have some special requirements that we don't know about... based on the file you provided.  But certainly there is nothing wrong with the file from Studio at all.  All that happened is that the target translation has been added.  The rest of the file is exactly the same as the source.

Thank you for looking into this.

I have asked the customer, who's been in contact with Easygenerator before, to ask about their XLIFF requirements. I'll paste here their reply.