×
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.
On 27 Feb 2013 17:51, Vernon Hamberg wrote:
My tests show that CPYFRMIMPF doesn't even correctly process UTF-16
BE with/without BOM.
It seems to do a byte-to-byte conversion, not a
character-to-character.
Using the v5r3 code, the CPYFRMIMPF does fine with UTF-16 data when
the STMF is tagged with CCSID=1200. When the STMF is improperly tagged
with CCSID=819 [for example], but the data is actually UTF16, then the
effect is a single-byte conversion. The proper results however did
require that the first line of text be empty, and thus FROMRCD(2) to
skip the empty line; i.e. in order to bypass the FFEF.
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.
midrange.com
