Codes created with CodeFinder option are not escaped

[Former user]

Original issue 341 created by @ysavourel on 2013-05-31T19:37:20.000Z:

When the codeFinder option is set, the original data of the new inline code is not escaped back, so the merged document is invalid.

the issue is in postProcessTextUnit() of AbstractMarkupEventBuilder when the codes are not processed after codeFinder is called.

There is an issue with having null encoder too that may be the reason why the current code is commented out.

This issue affects any AbtractMarkupFilter, including XMLStreamFilter and HTMLFilter.

[Jim Hargrave (OLD)]

I would argue that codefinder rules generate internal data that should not be escaped. This is the job of the encoder using the ENcoderContext.INLINE