Unknown said:

Thank you, in advance, for any suggestions.

Can you provide a sample file?  Just copy one, remove everything apart from a couple of complete "unit" elements and attach to here.

Hi Paul,

I still have your email address, so I've sent it that way. Please let me know if you have any questions.

Best, Mindy

Thanks for the file.  It's actually an XLIFF 2.0 file and not strictly a bilingual XML.  So if you rename it to XLIFF even Studio 2017 should be able to handle this.  However, it is also invalid as the sc element in there should have an id attribute.  This is mandatory according to the XLIFF specification:

http://docs.oasis-open.org/xliff/xliff-core/v2.1/os/xliff-core-v2.1-os.html#sc

Your file has this sort of thing and misses the id:

<sc type="fmt" dataRef="boldStart"/>

I think there are also other problems in the file preventing it from validating correctly as I still had problems even after correcting this so really you should give this back to your customer and ask them to provide a valid file.

We are working on a new multilingual XML filetype that can actually handle this file without a problem because it doesn't care about all the rules around what's correct and what's not, it only needs to now where to find the translatable text for source and target.  But this will only be available in 2021 and won't be released to the appstore for a few weeks yet.  So until then your options are probably not great and would either require some regex search & replace work on the natïve files so you can handle as monolingual XML, or you ask your customer to provide valid XLIFF 2.0 files and then you shouldn't have a problem.

Thanks for the file.  It's actually an XLIFF 2.0 file and not strictly a bilingual XML.  So if you rename it to XLIFF even Studio 2017 should be able to handle this.  However, it is also invalid as the sc element in there should have an id attribute.  This is mandatory according to the XLIFF specification:

http://docs.oasis-open.org/xliff/xliff-core/v2.1/os/xliff-core-v2.1-os.html#sc

Your file has this sort of thing and misses the id:

<sc type="fmt" dataRef="boldStart"/>

I think there are also other problems in the file preventing it from validating correctly as I still had problems even after correcting this so really you should give this back to your customer and ask them to provide a valid file.

We are working on a new multilingual XML filetype that can actually handle this file without a problem because it doesn't care about all the rules around what's correct and what's not, it only needs to now where to find the translatable text for source and target.  But this will only be available in 2021 and won't be released to the appstore for a few weeks yet.  So until then your options are probably not great and would either require some regex search & replace work on the natïve files so you can handle as monolingual XML, or you ask your customer to provide valid XLIFF 2.0 files and then you shouldn't have a problem.

Thanks, Paul. Yes, we have always gotten XML files from them, as we got the error you mentioned in XLIFF format. It seems we have been doing these for a while now, and someone doesn't want to go back to the client and get correct files. I cannot even confirm what source program they are exporting it from. 

You might find this new filetype could solve your problems here:

https://community.rws.com/product-groups/translationproductivity/w/customer-experience/6039/multilingual-xml-filetype