Aubeline Brandamir 

It sounds to me as though the xliff file is invalid.  Can you share the file?

Hello Paul ,

Sure! File is sent to your email.

Thank you!

Thanks Aubeline Brandamir 

ok - the file is definitely invalid XLIFF as reported by Studio in your error message.  You can test this here if you like:

https://dev.maxprograms.com/Validation/

Out of the box Trados Studio isn't lenient with files like this so you won't be able to manage it out of the box.  You could create a custom XML filetype for it but your file is fully populated with target translations already so using a monolingual XML filetype wont help.

On the appstore we have a Multilingual XML filetype and this is great for handling crappy bilingual files as it's very lenient and will extract whatever you tell it to and ignore all the rules.  I tested it with your file using these settings:

That's it, I didn't need to configure anything else and this allows me to translate the file.

The downside is I won't be able to change the "state" of the translations.  Your file contains two states:

<segment id="0" state="reviewed">

<segment id="4" state="translated">

But what you could do is use an expression when picking up the source/target content to only extract the content you need for translation.  This way you could, for example, only extract the segments that have a "translated" state and make any changes needed to review them.  Then at the end just search replace the "translated" state with "reviewed"... IF this is even enecessary.

Anyway... long story, but the knub of it is your XLF file is invalid so you will only be able to handle this in the tool that created it, or by using the Multilingual XML filetype as explained.  I'll reply to your email with a screenshot of what gets extracted so you can see.

Thanks Aubeline Brandamir 

ok - the file is definitely invalid XLIFF as reported by Studio in your error message.  You can test this here if you like:

https://dev.maxprograms.com/Validation/

Out of the box Trados Studio isn't lenient with files like this so you won't be able to manage it out of the box.  You could create a custom XML filetype for it but your file is fully populated with target translations already so using a monolingual XML filetype wont help.

On the appstore we have a Multilingual XML filetype and this is great for handling crappy bilingual files as it's very lenient and will extract whatever you tell it to and ignore all the rules.  I tested it with your file using these settings:

That's it, I didn't need to configure anything else and this allows me to translate the file.

The downside is I won't be able to change the "state" of the translations.  Your file contains two states:

<segment id="0" state="reviewed">

<segment id="4" state="translated">

But what you could do is use an expression when picking up the source/target content to only extract the content you need for translation.  This way you could, for example, only extract the segments that have a "translated" state and make any changes needed to review them.  Then at the end just search replace the "translated" state with "reviewed"... IF this is even enecessary.

Anyway... long story, but the knub of it is your XLF file is invalid so you will only be able to handle this in the tool that created it, or by using the Multilingual XML filetype as explained.  I'll reply to your email with a screenshot of what gets extracted so you can see.

Hello Paul,

Thank you for your prompt and detailed feedback!

I've just used the settings you suggested and indeed, I can now safely open the file in Studio. I still have one issue however: the target segments are empty.

This is a revision job, so all translations should be populated.

Aubeline Brandamir 

When using this filetype you have to run the import multilingual xml batch task after the project is created.  Check the wiki...  Multilingual XML FileType 

That's how we get around segmentation and can better support crappy files like Wordpress XLIFF where large html content gets dropped into a single XLIFF translation unit as CDATA for example.