Can you post brief sample file ?

Hi Dmitry Zaretsky

Yes the link you provided alongside this helpful resource,  https://m.youtube.com/watch?v=kPaHs5xjWyU should work.

I tested to ensure I had the same scenario where in a cell I had a soft return and tags (due to formatting)

Please see source sample and how I got it to display in Studio

To confirm the steps I took.

1. Edit Segment Settings by adding a new one

2. Before Break + After Break = Anything

3. Advanced View and gave it a description

4. Before Break = .[\n]+

5. After Break = .

TIP: You do need to recreate your sdlxliff files against the amended TM.

I hope this confirms it is possible and that I gave you enough guidance and clarity to get it working. If you still require support please confirm what are your segmentation rules?

Lyds

Ryszard Wania

If these are tags as a result of the embedded content processor why don't you just exclude them in the embedded content processing rules?  That is far easier to manage.

Paul

Same situation here. I have already sent the files to you. Even if the tag pairs in embedded content are declared to be excluded it does not work... Studio 2021.
BTW, changing the segmentation rules as suggested by Lydia does not work also.

Jerzy Czopik

Not the same Jerzy.  Apologies... I forgot to get back to you.  Your file was XLIFF and the embedded content is actually html entities.  This causes a problem for the following reasons:

1. out of the box XLIFF filetype can't handle this at all in terms of being able to re-segment
2. the multilingual XML filetype can normally resolve this, but not if the embedded content is an html entity.  This is because we are still relying on the Trados Studio API and the way it handles the embedded content isn't optimised to support this.  It would need a significant change (improvement) to manage this in the way you'd like to use it

  There is no easy workaround for you I'm afraid other than handle as a monolingual XML.  So move the source into the target, translate the target and lose the value you get from the pre-translated target in the XLIFF.

Paul

Dear Paul, many thanks for the explanation. In this case we will have to live with that. The task was to post-edit, not to translate. But knowing this I will try to convince the customer to run the whole process differently.

Good evening Paul and thank you very much for your reply. That actually solved everything - I used the "Exclude" option:

Just one more question: In this project, I have only tags at the beginning/end of segments. But if there was a text with some HTML coding in the middle of sentence, would this option split the sentence into two segments? I mean sentence like "Turn the <b>device</b> on"?

Good evening Lydia,

Thank you for your reply but this is exactly what I did and it did not work in this particular case. Paul's solution did the magic.

Have a nice evening

Wonderful Ryszard Wania as I was wondering what was bringing in those tags - as per my sample file :) 

Ryszard Wania

If you use a catch all rule then yes. But if you are more specific with your rules then no. You could create inline rules and also exclude rules to suit the tags and how you’d like to see them handled.