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



A little more on what the code is - here is what I believe is processing the nodes in question -

when event = *XML_UCS2_REF
or event = *XML_ATTR_UCS2_REF;
stackval(depth) += %char(%subst( ucs2val : 1
: %div(stringLen:2) ));

UCS2VAL is declared as a data type C, that's all.

We are at 7.1 of the OS, so I think we do not have the newer support for CCSIDs and all.

How about changing UCS2VAL to and H type? Then do whatever we need to do with it?

Or have a table with a column that is UTF-8? And pull into the variable association with that? Am I being crazy?

Regards
Vern

On 2/13/2017 3:29 PM, Vernon Hamberg wrote:
Y'all

We have data coming in that MIGHT contain emojis - not sure if we can have a corporate rule to say don't do that, but it still might.

We are using XML-SAX to process the XML - it works fine - until someone puts an emoji to send the customer a bouquet or a nice face.

I've suggested the source app put the text in a CDATA block - does this look as if it should work?

If not, other suggestions are welcome.

Emojjs appear to have their own block in Unicode - the one's I saw appeared to be 4-byte sequences - but I see there can be several lengths, as, IIRC, UTF-8 can have.

I've wondered about using a 1208-CCSID variable to pull in the data - I'm trying to find where the source code is hiding right now!

Help much appreciated!

Vern


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.