Re: CPYFRMIMPF and Unicode - UTF-16 in particular -- MIDRANGE-L

Subject: Re: CPYFRMIMPF and Unicode - UTF-16 in particular
From: CRPence <CRPbottle@xxxxxxxxx>
Date: Sat, 02 Mar 2013 08:59:43 -0800
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>

On 01 Mar 2013 23:22, Vernon Hamberg wrote:

I agree with your suggestions - trouble is, the scenario doesn't
match their use. The files are being saved, perhaps, from Notepad,
and we don't know which encoding the user chooses.

Sorry. I was not meaning to address anything other than big-endian UTF-16 and the "with or w/out BOM" claim. My point was to refute the claim that all the variations of UTF-16 were nonfunctional... by pointing out that the CPYFRMIMPF worked fine for the endian-ness of the system, but with the BOM, the feature does not ignore them as valid data; and that CCSID is 1200.

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Re: CPYFRMIMPF and Unicode - UTF-16 in particular , Vernon Hamberg

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.