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

Hi Nathan

One problem - we are at 7.1 - I don't think I have an easy way to get long
enough variable in UTF-8 in RPG - but I could do what I do now - read the
IFS into a variable without text conversion. Then find any problematic
characters.

I just don't think that is practical - there are almost 8,000 valid UTF-8
byte strings in a table I'm using now, I don't think I want to go looking
through the XML for byte strings I want to eliminate - some of these are
possible valid.

My main question was, do I understand what is happening, and is there some
way to know the byte= position where the problem occurred.

Cheers
Vern


On 7/11/2017 5:55 PM, Nathan Andelin wrote:

Vern,

If the XML parser is having trouble with certain characters, my
inclination
would be to read the XML data (i.e. file) and filter out unwanted
characters before feeding the stream to the parser. By filter, I mean only
allowing characters within a certain Hex or Decimal range into the output
stream.

--
This is the RPG programming on the IBM i (AS/400 and iSeries) (RPG400-L)
mailing list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: http://amzn.to/2dEadiD