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

Exactly - and right now I don't want to be replacing stuff in this fashion - no need at this time - maybe if we used the euro-style CCSID we'd have that, if we needed it - a thought for later - the XMLTABLE lets you specify the ccsid that the function moves the data into.

Cheers
Vern

On 7/12/2017 1:26 PM, Henrik Rützou wrote:

Vernon,

a 3 byte UTF-8 character may be or may not be supported in EBCDIC depending
on the EBCDIC CCSid. ...


// Replacing Microsoft Smart Quotes
myField = replaceUTF8unit(myField:'E28098':'''':819);
myField = replaceUTF8unit(myField:'E28099':'''':819);
myField = replaceUTF8unit(myField:'E2809C':'"':819);
myField = replaceUTF8unit(myField:'E2809D':'"':819);
myField = replaceUTF8unit(myField:'E28093':'-':819);
myField = replaceUTF8unit(myField:'E28094':'--':819);
myField = replaceUTF8unit(myField:'E280A6':'...':819);

// Replacing EUR Sign with Text
myField = replaceUTF8unit(myField:'E282AC':'EUR':819);

On Wed, Jul 12, 2017 at 8:14 PM, Vernon Hamberg <vhamberg@xxxxxxxxxxxxxxx>
wrote:

Henrik

Exactly - in the case I just found, the UTF-8 byte string was 3 bytes -
the HORIZONTAL ELLIPSIS. It preceded the emoji, which was at byte # 381 -
but XML-SAX said the error was at position 379 - that lead me to think that
the count was of characters, the emoji is 1 character - as you describe
here - so that was correct if by character, not if by bytes.

The SQL approach is showing much promise!

Thanks
Vern


On 7/12/2017 12:52 PM, Henrik Rützou wrote:

The thing that exactly goes wrong here is that UTF-8 is a 1-4 single byte
unicode encoding,
UTF-16 i a 1-2 double byte unicode encoding and UTF-32 is a 4 byte
encoding.

In other words, you need 4 bytes to cover the full range of Unicode

EBCDIC and ASCII is a single byte encoding so there is no way you are able
to cover
the whole range of Unicode in 256 characters.

UCS-2 is a double byte encoding so there is no way you are able to cover
the whole
range of Unicode in 65.536 characters

The emojies probably has a value beyond the 64K limit of UCS-2 and that is
why it
fails because they will need 2 UCS-2 characters each 2 bytes long = 4
bytes
and
that is not supported by ICONV

So in any case the XML unicode has to be cleaned up so it either fits
EBCDIC or UCS-2
it is as simple as that.



On Wed, Jul 12, 2017 at 7:01 PM, Mike Jones <mike.jones.sysdev@xxxxxxxxx>
wrote:

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