Re: XML Toolkit and CDATA elements

[Scott Klement <rpg400-l@xxxxxxxxxxxxxxxx>]

Hi Paul,

That's because IFS files are tagged with a CCSID.  When you read an IFS 
file, you can determine it's CCSID from the "object description"...  I'm 
guessing that the XML Toolkit tries that CCSID in preference to the 
encoding attribute.

On the other hand, when the data is kept in a variable and passed to the 
API via parameters, there's no CCSID attribute to go by.  So it has to 
rely on the encoding.

Just a guess, mind you...  but it would explain what's happening...

You might consider constructing your XML data in unicode.  RPG has 
excellent support for UCS-2 and UTF-16 Unicode.  If you construct your 
data in Unicode instead of EBCDIC, you theoretically won't have the same 
problem.

Incidentally, just for the fun of it, I ran your sample XML document 
(the one with <![CDATA[) through Expat and it worked okay in Expat. 
Granted, I didn't try changing my job CCSID to a non-37 value, so it 
probably wasn't a very good test :)



Paul Nicolay wrote:
> Scott,
>  
> I can understand the bracket issue, but the strange thing is that without the CDATA element, I neither can parse anything apart from those XML's that use encoding ibm037 (while for documents in the IFS the encoding doesn't matter at all, everything works).
>  
> Anyway, I'll try once more to get everything in sync related to CCSID possibilities.
>  
> Kind regards,
> Paul
>
> ________________________________
>
> Van: rpg400-l-bounces@xxxxxxxxxxxx namens Scott Klement
> Verzonden: vr 5/12/2008 00:08
> Aan: RPG programming on the IBM i / System i
> Onderwerp: Re: XML Toolkit and CDATA elements
>
>
>
> Hi Paul,
>
> Everything you say seems to point at a CCSID problem.  The square
> bracket [ character is notoriously difficult to deal with in EBCDIC
>
> Since your encoding is set to ibm037 -- please make extra sure that the
> CCSID of your RPG source code is CCSID 37. (Which would be odd, since if
> I recall correctly, you don't live in a country that uses 37 by default)
> If not, make corrections accordingly.