Aubeline Brandamir 

Aubeline Brandamir said:

1. Yes, it is a mxliff file

So this means it will be opened using the memsource filetype by default unless you do something to prevent this.  I am surprised to see these placeholders being ignored in 2024 though... perhaps this is a bug... perhaps there is something odd about your file... perhaps you are actually not using the mxliff filetype to handle this.  Can you provide a screenshot of your filetype settings page so we can see which XLIFF filetype are activated and in what order?  If the memsource filetype is first and if it's activated have you added a mask for *.mxliff in the "File dialog wildcard expression" field to ensure the XLIFF filetype will even open it?

Any chance we can see the file?  You can send it to pfilkin at sdl dotcom is this is acceptable?

 Aubeline Brandamir 

Aubeline Brandamir said:

1. Yes, it is a mxliff file

So this means it will be opened using the memsource filetype by default unless you do something to prevent this.  I am surprised to see these placeholders being ignored in 2024 though... perhaps this is a bug... perhaps there is something odd about your file... perhaps you are actually not using the mxliff filetype to handle this.  Can you provide a screenshot of your filetype settings page so we can see which XLIFF filetype are activated and in what order?  If the memsource filetype is first and if it's activated have you added a mask for *.mxliff in the "File dialog wildcard expression" field to ensure the XLIFF filetype will even open it?

Any chance we can see the file?  You can send it to pfilkin at sdl dotcom is this is acceptable?

Thanks Paul!

I've sent all via a pm

I've tried a few things so maybe the "settings" pile up now

Aubeline Brandamir 

I am a bit confused about why you have this problem to be honest.

I did wonder at first why you had two, but then I remembered Jesse Good developed one and the Trados AppStore Team took it over - https://appstore.rws.com/Plugin/29 - when he stopped supporting it.  I believe the first one in your list is the AppStore version, so this should be ok.  I tested it and it seems fine:

Then, I unchecked both of them and added the embedded content regex to the default XLIFF, added *.mxliff to the "File dialog wildcard expression" field and this also works fine... screenshot would be exactly the same, so I didn't bother ;-)

So, you shouldn't have a problem.  But then I opened the SDLXLIFF you also sent me and this has been created using the default memsource filetype and not the AppStore version.  Based on the screenshot of your settings this would be impossible, so I can conclude you did not create your project with the settings you showed me.  Therefore you need to check what project template you used to create your projects with because it clearly isn't your File -> Options.

Thank you so much for your thorough explanation Paul!

I've gone over your message a few times and did a few tests, and I finally managed to get those tags to appear as tags! And now I understand the problem. Yeaahh!!

You're a lifesaver, as always!

The issue may come from the fact I jump from 2022 to 2024 because of the fact Aspic Xbench and Antidote appear to still not work in Studio 2024, so I go to the older version for those. I admit I did not yet find the time to look into this really. So I may have used 2022 and forgot about it, honestly!

Could this also explain why the segment status (draft, confirmed...) also do not appear properly in Phrase after the import?