How to exclude placeholders enclosed in single or double curly brackets in HTML files?

Question

I'm trying to define text enclosed in single or double curly brackets in an HTML file as placeholders. For example.

Do not translate this {{ variable }} and don't translate that { variable } either.

The following expression works fine Notepad++, but it doesn't work in SDL Studio. \{+[^}]+\}+ 1. Why doesn't the expression work? 1. What regex flavor(s) does SDL Studio support?

Paul · Answer

Hans Kröger 
 The information missing is how you set up the embedded content rule as this provides Studio with the information it needs so it applies your rule in the right context. For example.... I created this: 
 
 The variables are located in three different elements (h1, p and time). So for this to work I need to specify the following in the html filetype: 
 
 This is of curse assuming the variables are in elements like this. If they are within server side scripts then you need to use the appropriate "Server side scripts" option. 
 Perhaps this helps? For my simple test file it works just fine:

Paul · Answer

ok Hans Kröger 
 It is difficult because the html parser is based on looking at files that are ordered with text always coming inside the elements. 
 The embedded content parser looks at what's inside the elements and treats them as text which is what allows you to handle your variables. 
 If you now inject script outside of these elements then you can only define an embedded processor to handle the content between the highest parent element... in your case the <html> element by the sounds f it. So in effect you are now saying treat the entire file as text and you'll define the rules for everything. 
 This will be quite tricky but if you're happy to handle everything as placeables it's easy enough:

Gets you this: 
 
 It's not too bad because structural elements will be moved out and you won't make a mistake. Inline tags, which I don't have in this example will be trickier since they won't be handled as opening and closing pairs and the translator will have to be very diligent to make sure they are placed in the right order. 
 Frankly, I think that if this type of file is something we're going to be seeing more and more of then it would be worth developing a filetype to handle this sort of embedded content in a different way. Perhaps you should raise this here and see if anyone else thinks it's a good idea: 
 http://ideas.sdl.com

Paul · Answer

Anthony Rudd 
 Same for 2019... but only the new Word filetype:

Trados Studio > 5. Regex and XPath

How to exclude placeholders enclosed in single or double curly brackets in HTML files?