When unparsing, if the infoset contains an escape character followed by another character, the unparsed document currently contains two instances of the escape character, and the following character is removed. For example:
escapeChar = /, escapeEscapeChar = \
In this case, I would think we expect the input to be:
However, the unparser is coming up with:
Something similar is happening with escape blocks. I've created parserTestCase equivalents for the tests. The parse equivalent for the first test behaves as expected. The second is experiencing memory issues (
DFDL-1315 - Escape block test using escapeEscapeCharacter using large amounts of Java Heap Space ).
in the following files: