Re: 5250 And Unicode -- MIDRANGE-L

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

Subject: Re: 5250 And Unicode
From: James Lampert <jamesl@xxxxxxxxxxxxxxxxx>
Date: Mon, 30 Apr 2012 11:24:37 -0700
List-archive: <http://archive.midrange.com/midrange-l>
List-help: <mailto:midrange-l-request@midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.midrange.com>
List-post: <mailto:midrange-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

Rich Loeber wrote:

I really just have a single character string within the display that needs
to be converted from CCSID 13488 (unicode UCS_2) into our normal 65535
encoding so that it will be readable.

So far, nothing easy is jumping out at me. Still searching the IBM site.

Table look-up is easy. It's just really, really, tedious and error-prone, when you're initially generating the tables.

--
JHHL

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

RE: 5250 And Unicode , DeLong, Eric
Re: 5250 And Unicode , Rich Loeber

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.