Katerina Mlejnkova 

Your start and end tag expressions are wrong.

Start tag will be something like this:

<li>

End tag like this:

</li>

The idea being your translatable content is the content between these tags.  So the rule should also be translatable, not "Not translatable".

I Think i solved similar problem.
When I use start and end tags (example <strong></strong>) in preview, I don´t see corect result.
That meaning in segments I see whole text with HTML code.
So this solving for me don´t work.

result after filter regex

Michal Honc 

Please provide an example of the actual file.  If you can cut it down to a few lines that represent your problem it would be helpful.  I can see from your rule that you still did it wrong by making it non-translatable, but I don't think that is where the problem really lies.

Hi Paul,
thank you for your fast answer.
Good view on my screenshot. It is only one variant of more when I tried. Normally I choice "Translatable".
I have Studio Trados 2022 with last updates.
Real setting:

Preview on testing file after use filter on HTML code (example <strong>)

Michal Honc 

Not exactly the test file I asked for!  So I made one up:

tags.yaml

Using this file, and importantly setting the Document Structure to "Node" it seems to work.  I only added one rule to test this:

Michal Honc 

Of course if your file uses the scalar operator like this one then it's better to use the embedded content filters:

scalars.yaml

Which is why you should always provide a sample... it's not that difficult!

Bingo, just my a small mistake. This is the solution "Node". Big thanks Paul.
I did not remember how to set about Document Structure Information.