× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Scott,

There's a CCSID attribute... it's the one you specify on the QxmlMemBufInputSource_new API.

The funny thing is that it doesn't matter what you set it to... Qxml_JOBCCSID, Qxml_CCSID37 or Qxml_UNICODE, the parsing only goes fine if the message itself has encoding="ibm037" specified ?

Kind regards,
Paul

________________________________

Van: rpg400-l-bounces@xxxxxxxxxxxx namens Scott Klement
Verzonden: vr 5/12/2008 10:45
Aan: RPG programming on the IBM i / System i
Onderwerp: Re: XML Toolkit and CDATA elements



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.




As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.