xml_SpecialCharactersSample.zip (9.8 KB)
@mbowen and @alchemiz I’m sharing a little sample of that illustrates that problem that I’m having.
Take note of the mapper after the XML Generator. In the mapper I use the string.replace() method. If I don’t do this, then the pipeline fails once it gets to the XML Parser that is downstream. By doing this, it also allows the XML formatter to complete successfully, however, I don’t wish to have the rendered symbol, but rather, I want to have the escape character code, just like the < and > remain intact.
How can I get either these 3 snaps (XML Generator, XML Parser, and XML Formatter) to treat all escape codes the same as it does for < and >, or how can I create customized snaps that are based on these 3 snaps. I am working against a deadline of June 16th, 2021 and this predictament is a big blocker for me.
Thanks, Alex
Thank you @alchemiz for the wonderful little pipeline.
@alex.panganiban.guild, you are correct that the Escape Special Characters option in the XML Generator snap only escapes these five entities: gt, lt, quot, amp, apos.
The snap is currently using a minimal xml escape handler, however, other snaps use a custom handler. So, this snap could also be updated to recognize/escape more xml.
Under the hood, the xml is parsed and transformed. It’s during the transformation that the register mark (®) gets converted to a glyph (symbol). We may be able control this behavior too.
Creating a support ticket would allow for this work to get started, however, it likely would be completed and available by June 16.
Let me evaluate your sample pipeline and see if we can get a workaround in place that can help you sooner!
