Thanks for the suggestion Scott. I will give it a try.

Regards

On Mon, 6 Jun 2022 at 03:37, Scott Klement <opensource@xxxxxxxxxxxxxxxx>
wrote:

YAJL work n Unicode -- not in a "market specific CCSID". Paste your
document into https://jsonlint.com/ and check that it is valid. If it
is not, please correct it. If it is, then things are going awry when
you are translating it to EBCDIC -- I recommend eliminating that step
and keeping it in Unicode until after it has finished parsing.

And stop staying "iSeries", the iSeries was discontinued in 2006.

--
Scott Klement
sk@xxxxxxxxxxxxxxxx

On 6/5/2022 10:42 AM, Sairam P wrote:
Hello,

We are using yajl_buf_load_tree parser to load data (JSON format) which
is
coming from an external source.

Most of the load does work as expected. Except, one field. Where, we
receive free format text characters which may contain special characters
and currency symbols.

When we receive the EURO symbol in that char field, the program fails
with
"lexical error: invalid character inside string". We are using market
specific CCSID (for european markets) to invoke the JSON parsing job in
iSeries.

Is there a way to load the data with the euro symbol into iSeries using
any
of the YAJL techniques? Please help.

Regards.
--
This is the IBMi Open Source Roundtable (OpenSource) mailing list
To post a message email: OpenSource@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/opensource
or email: OpenSource-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/opensource.

Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

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

This mailing list archive is Copyright 1997-2022 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.