Re: Having a problem with HTTP_xlatep in HTTPAPI -- UTF-8 is getting treated as Latin 1 -- MIDRANGE-L

Subject: Re: Having a problem with HTTP_xlatep in HTTPAPI -- UTF-8 is getting treated as Latin 1
From: "James H. H. Lampert" <jamesl@xxxxxxxxxxxxxxxxx>
Date: Fri, 25 Jul 2025 09:54:43 -0700
List-archive: <https://archive.midrange.com/midrange-l/>
List-post: <mailto:midrange-l@lists.midrange.com>
List-subscribe: <https://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@lists.midrange.com?subject=subscribe>
List-unsubscribe: <https://lists.midrange.com/mailman/options/midrange-l>, <mailto:midrange-l-request@lists.midrange.com?subject=unsubscribe>

On 7/24/25 11:22 AM, I wrote:

I think I've seen this before. I've got a

CALLP HTTP_xlatep(500000:%addr(buffy):TO_EBCDIC)

on some UTF-8 data I've read from a web service, and there's a "lowercase a with acute accent" that's being treated as if it were Latin-1 data, so it comes out garbled to "uppercase A with tilde" followed by an "inverted exclamation point."

FWIW, some inspiration finally struck me about an hour later, although it took quite a bit of reading in the HTTPAPI_H member to dope out the exact call needed.

CALLP HTTP_SetCCSIDs(1208: 37: 1208: 37)

It's apparently the second pair of CCSIDs that affects HTTP_xlatep. But I could be mistaken.

--
JHHL

As an Amazon Associate we earn from qualifying purchases.

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