|
Vernon,
here is a trick:
Change the xml-file to cssid 819 then you should be able to read the XML.
Now you have UTF-8 garbage in some XML "text" fields but they can be handle.
On Wed, Jul 12, 2017 at 10:57 AM, Vernon Hamberg <vhamberg@xxxxxxxxxxxxxxx>
wrote:
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
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.