Re: XML-SAX *XML_EXCEPTION event and reported parsed length question

On Thu, Jul 13, 2017 at 6:01 PM, Nathan Andelin <nandelin@xxxxxxxxx> wrote:

BTW, I'm now looking at the SQL XMLTABLE approach - it takes it all in
nicely from an IFS file tagged as 1208, converts to EBCDIC where it can,
and gives me x'3F' otherwise - all with no errors at all for parsing.

Couldn't you copy the UTF-8 stream file (CCSID = 1208) to a new stream file
that has a CCSID 819 (ASCII) or some other CCSID that filters out EMOJI,
before attempting to parse it?

That was the basic idea of my suggestion, though I would recommend
against 819 (no need to be that restrictive). I actually thought this
was merely a minor variation on your original filtering suggestion.
But it would seem XMLTABLE happens to provide both filtering and
parsing, which is an unbeatably attractive proposition for Vern (and
I'm sure for many folks). He seems to be happily going down the
XMLTABLE path now; I see no reason to try to pull him off it at this
point.

John Y.