We have very often the following situation:

Customer sends so called XLIFF, where you have CDATA sections with HTML inside. So far quite simple, treat XLIFF as XML and parse the content with the HTML embedded file type.

But then the files do contain more content, which could be locked, like {lock me} or similar. When going the XML way with HTML parser there is no more possibility to parse anything else. When I take the XLIFF with the embedded content, I need to write rules for dozens of elements, which is quite ridiculous - all the rules are already there, in the HTML parser...

So now how could I parse the rest? Is there any way to get another file type on top? The best way would be to take the regex parser as next, but as far as I can see it is not possible now. Could you make it possible in the future? And in the meantime how could I parse this content?

MTIA and best regards, Jerzy