I probably won't be able to help much, but the first place I would check would be the segmentation rules, which in Studio are defined inside the translation memory used. If you've been messing with segmentation, maybe check that the default segmentation rules are still being used (one should be called "Full stop", which should usually break segments at a period). Otherwise, it will have to do with something deeper, i.e. perhaps how the tags are being parsed.

Thank you! I've already gone back to the default settings just in case, but it didn't help.

Alejandro Mestre Vives 

Why don't you send me a sample file you have problems with?  It's going to be nearly impossible to help you otherwise.  You can send to pfilkin at rws dotcom if that works for you?

Alejandro Mestre Vives 

I can achieve this:

Try the attached project template settings: ML_XML_XLF.zip

It's not perfect because there are limitations when using the Multilingual XML filetype for bilingual content, but given your target isn't actually translated yet you can simply copy source to target and overwrite everything that gets imported to make it easier before you start.

The most important thing is you achieve your segmentation!

The only thing I can achieve (after creating a new project selecting the template indicated and the respective file) is this:

and this (after opening the project and looking for the somehow hidden file):

So I thank you for your help, Paul. But as this is becomming a little bit too time-consuming I would say I'll try something else in cooperation with the customer's IT section may be.

Thank you again

Alejandro Mestre Vives 

Are you sure you have installed the Multilingual XML filetype?  And if you have what version of Trados Studio are you using?

Sorry, I forgot. Trying to download now:

My version is 2021 btw.

Alejandro Mestre Vives 

Alejandro Mestre Vives said:

Sorry, I forgot.

No wonder you could not make it work!!

Couple of things now:

1. you are getting that error because you are attempting to download from the appstore.sdl.com and have completely ignored the message you will have seen when you first went there.  Please use the  (Missing Wiki Page) 
2. the template I gave you might not work as this was for 2022 and I think (not 100% sure) the filetype ID may have changed between versions.  Try it and see.  If it doesn't work I'll create a 2021 version.

Ok, seems to be right. It's doesn't work with 2021. Looks like the last editor window above ...

Alejandro Mestre Vives 

Alejandro Mestre Vives said:

Ok, seems to be right. It's doesn't work with 2021.

The set up is actually very simple.  Try this:

Thank you. Same result. Just to be sure, I send you all my window settings right now:

Alejandro Mestre Vives 

My guess here is that you are not even using this filetype for your project.  I bet your file is still being processed with the XLIFF 2.0 processor.  You should check that first.

The reason I'm feeling confident to say this is that you have this:

The extension of the file you sent me was *.xlf

So it won't even be getting picked up when you create your project.

Alejandro Mestre Vives 

My guess here is that you are not even using this filetype for your project.  I bet your file is still being processed with the XLIFF 2.0 processor.  You should check that first.

The reason I'm feeling confident to say this is that you have this:

The extension of the file you sent me was *.xlf

So it won't even be getting picked up when you create your project.

You mean it should be an *.xml or *.xliff file? Could it be converted?

Alejandro Mestre Vives 

No... I mean you should add the appropriate mask to your filetype settings.  So this for example:

*.xlf

Or:

*.xliff;*.xlf

Or

*.xml;*.xliff;*.xlf

Whatever you want as long as *.xlf is in there.

Well, at least something happend. I added *.xlf and got this in return (editor window):

Alejandro Mestre Vives 

You also didn't enable embedded content processing, so don't expect that to work anyway.

The filename of the file you are using is not the same as the one you sent me so I cannot comment.

Frankly... after all of this I think you should go back and review the wiki and video properly for this filetype.  Then revisit it!  I think there is too much guessing going on here.

Great success! Got this now:

May be just a matter of placeholders now, right?

Alejandro Mestre Vives 

Looks as though you have still not enabled the embedded content processor for html.  That would take care of your tags.  You also don't seem to have used the import multilingual xml batch task to bring in the target content.

Ok, I think I almost got it! Though it's not quite a plug-and-play story :) If I only could get rid of this §@#'!!! "Object reference not set to an instance of an object" error message, may be I could start my work.

I started a completely new project to remove the error according your "workaround A", but it's a never ending story: to create a new project I have to add at least one file with the original settings of the Multiligual XML add-on. Then I get a translation file that has to be removed (because it doesn't include the right processing) and readded again processed with the new right settings. Then I get the error message again ...

But I'll find a way. Thank you.

Hi, it's me again. The Trados editor finally looked quite fine:

As you can see I translated some segments. Problem now is that the output (just to test it) doesn't show any translations (not with normal Target translations command nor with Multilingual translations:

Any idea?