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

Jon

Emojis is just the same as handling forreign characters. If you construct
your system to handle
emojis the system will also handle any character (such as arabic or
chinees) you throw at it and
vice versa.

The real showstopper is the ancient 5250 that only will be able to display
characters defined in
ASCII 7 bit - all other characters will either be garbage or even 5250
control characters.

But you can treat incomming UTF-8 byte for byte using ASCII 8 bit as the
intermediate CCSid and
convert it to EBCDIC and the EBCDIC string can be converted back to UTF-8
by converting it byte
for byte also using ASCII 8 bit as the itermediate CCSid.

The reason that you can do that is that 8 bit ASCII alway will have a
corresponding EBCDIC
character even though the character hex value in different EBCDIC CCSid may
vary.

So ICONV 819>37>819 or 819>277>819 will always give you a correct result
even though the
hex values in 37 isn't the same as in 277.

But when you do that every XML or JSON tool works since the XML/JSON
standard is build on 7 bit
ASCII in any special delimiter character and allowed element names. The
reason for that is that any
UTF single byte character below or equal to x'7F' is the same as 7 bit
ASCII and any other character
requires two or more bytes in UTF.

So the bottom line is that there is no difference between an emoji and a
chinese character and if
you want to treat such characters in an 8 bit EBCDIC environment it can be
done.


On Wed, Jul 12, 2017 at 10:03 PM, Jon Paris <jon.paris@xxxxxxxxxxxxxx>
wrote:

It is relatively trivial with XML-SAX and XML-INTO too Richard. Just not
when you've got emojis up the wall!

Emojis on a business system - shock - horror.


Jon Paris

www.partner400.com
www.SystemiDeveloper.com

On Jul 12, 2017, at 2:57 PM, Richard Schoen <Richard.Schoen@helpsystems.

com> wrote:

Vern,

Not sure if this is in your consideration, but VB.Net and C# make XML

handling quite trivial and you can interface easily to IBMi.

Regards,


Richard Schoen
Director of Document Management
e. richard.schoen@xxxxxxxxxxxxxxx
p. 952.486.6802
w. helpsystems.com
----------------------------------------------------------------------

message: 1
date: Wed, 12 Jul 2017 10:01:36 -0700
from: Mike Jones <mike.jones.sysdev@xxxxxxxxx>
subject: Re: XML-SAX *XML_EXCEPTION event and reported parsed length
question

Hi Vernon,

Three cheers for just considering using the SQL XML functionality

(XMLTABLE function), even if you don't end up using it.

I helped someone parse some XML on one of these forums once and had it

working using XMLTABLE in about an hour. Days later, the person was still
tinkering around trying to get the more laborious ways of parsing to work.

Best wishes for a speedy solution...

Mike

On Tue, Jul 11, 2017 at 2:50 PM, Vernon Hamberg <

vhamberg@xxxxxxxxxxxxxxx>

wrote:

I'm aware of - and would like to use - the SQL XML functionality,
which does NOT seem to have these problems - I've tried a few bits.
Problem is, it'd be a rewrite of this program.

Cheers
Vern

--
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

--
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