Re: CSVR4 and UTF-8

[Vernon Hamberg <vhamberg@xxxxxxxxxxxxxxx>]

I think probably, Sam - I suspect that the i is using that in WRKLNK, 
option 5 (also known as DSPF). And probably equally the SQL engine does.

Unless we can specify that the XML-SAX and XML-INTO opcodes can have the 
CCSID set to 1208 - you CAN have it set to UCS2, but that's not enough 
to prevent errors when the UTF-8 character is not in the UCS2 character 
set - emojis certainly are in this category, things like ellipsis and em 
dash get set to that X'3F' again.

But it's too late to use iconv, I am guessing, when you use those opcodes.

Maybe for consuming XML (not using SQL's capabilities), the DATA-INTO 
can be used and then something that uses iconv?

A very challenging task, we have, don't we?

Vern

On 5/5/2020 12:38 PM, Sam_L wrote:
> I admit my lack of experience or knowledge on this, but would the 
> iconv()--Code Conversion API be of any use?
>
> Sam
>
>
> On 5/5/2020 12:10 PM, Vernon Hamberg wrote:
> > Oh yeah - and I have a presentation on this problem in the iNSIGHT 
> > virtual COMMON conference that started today - I believe everything 
> > will be available for 60 days, one can still register for it. Have to 
> > be a COMMON member, probably.
> >
> > Vern
> >
> > On 5/5/2020 9:17 AM, Greg Wilburn wrote:
> > > So I changed the attributes of the file from 819 to 1208.  It 
> > > displays better in WRKLNK.  The Right Single Quote is displayed as a 
> > > blank instead of the other characters.
> > >
> > > I'm wondering if this will help (at least some).