Eva Repolusk-Stoppel 

Thanks for letting me share how we solved this one. I put it here:

You asked me a question on segmentation relating to this paragraph:

Also this one:

We can see that the German is segmented, but the English is not.  The reason for this is the reason why out  of the box Studio isn't very good at handling files like this and lumps everything into one segment in its bilingual filetype support.  We know for sure how to segment the source.  But we don't know how to segment the target.  It could be that there are less sentences in the target, or more sentences (because these are actually paragraphs)... depending on what was needed to create a decent translation.  So out of the box Studio lumps them all into one big segment.

To try and solve this we decided we should segment the source, ad then simply import the target into the first segment so you have it, and then you need to segment it yourself by splitting up the translation appropriately.  It's not perfect by any means, but at least we can then offer a segmented file for these sort of files that will allow you to work on them more comfortably.

I hope that explains?

Glad you managed to make this all work anyway!

 Eva Repolusk-Stoppel 

Thanks for letting me share how we solved this one. I put it here:

You asked me a question on segmentation relating to this paragraph:

Also this one:

We can see that the German is segmented, but the English is not.  The reason for this is the reason why out  of the box Studio isn't very good at handling files like this and lumps everything into one segment in its bilingual filetype support.  We know for sure how to segment the source.  But we don't know how to segment the target.  It could be that there are less sentences in the target, or more sentences (because these are actually paragraphs)... depending on what was needed to create a decent translation.  So out of the box Studio lumps them all into one big segment.

To try and solve this we decided we should segment the source, ad then simply import the target into the first segment so you have it, and then you need to segment it yourself by splitting up the translation appropriately.  It's not perfect by any means, but at least we can then offer a segmented file for these sort of files that will allow you to work on them more comfortably.

I hope that explains?

Glad you managed to make this all work anyway!

Thank you so much for solving this problem, that last explanation of behavior in terms of segmenting and for your work and help in general! It is so much more enjoyable to test the limits of Studio knowing that there is somebody who will figure it out eventually :-)

Paul , Eva Repolusk-Stoppel 

I had not realized that the Multilingual XML filter has that segmentation behaviour, but it's a good idea to handle a very complicated problem!

I developed a way (outside Studio) to handle bilingual XML files with alignment of both source and target, which I demonstrated here:

https://community.rws.com/product-groups/trados-portfolio/trados-studio/f/regex_and_xpath/32238/custom-bilingual-xml-with-html-embedded-content/106275

But it is technically much more complicated and only works if there is sufficient paragraph parity. So I am really impressed with how simply the multilingual XML file type handles that. Looks like I might have to employ it soon!

Daniel

Thanks for that... it's one of those things where most translators probably won't see the difficulty.  And that's understandable!!  But it is the main reason why the core team have never done this in the product.  So we took a more pragmatic approach to make sure the main problem of segmentation was resolved and the translator can do the rest.