This is the view in Phrase:

and this is what Studio thinks I should be seeing i.e. it goes from {6} straight to the bullet point item, missing out segment 11:

 Michael Bauer 

please provide a sample file. You won’t get a sensible answer without one.

I can't post it here, any way of sending it to you directly?

Send it to pfilkin at SDL dotcom and make sure you clarify exactly where the problem is unless it’s a small file.

Michael Bauer 

I don't know for sure, but it looks as though the XML encoding for the HTML-like tags in the source string (<b>***** **** ********:</b>{7}) may cause issues with how the Translation Unit is interpreted by Trados Studio. 

The easy workaround for now would be to either use the default XLIFF filetype which seems to handle this file really easily anyway, and extracts the content, or use the Multilingual XML filetype.  Both these filetypes will allow you to work with this file and extract the content you need.

I'll create an anonymised file with something to mirror this problem and send it to you for approval (something you should do anyway)... if you're happy I'll share that with the support team so we can log a potential bug.

Thanks for looking at this.

How do I make Studio treat mxliff as not-mxliff?

Michael Bauer 

Like this:

Many thanks, that seems to be doing the trick for now, fingers crossed no unexpected side effects. One thing - I don't know if that's of interest - I noticed is what when using mxliff in Studio 2022, all of a sudden after translation all units in Studio and on opening them in Phrase, all the translations would be there but the first one would be set to Unconfirmed and the rest to Confirmed. In 2019, using the same workflow, they would all be set to Unconfirmed. I don't need a fix for this, as it was easy enough to work around BUT I'm mentioning as it feels like 2022 is making a general hash of handling mxliff.