Re: CPYFRMIMPF and Unicode - UTF-16 in particular

Indeed. I repeated that assertion but with the eventual understanding that we were getting files tagged as 1252, which always resulted in a bytewise conversion, as you explained - I've learned a lot in this exchange!

Since I'm the OP, saying we want to process Unicode text files - well, I see where you could take that to mean properly-tagged stream files. A better statement of the problem might be, we want to process files that have Unicode content. That is the nice thing about these threads - things get clarified and better-stated.

Regards
Vern

On 3/5/2013 10:04 AM, CRPence wrote:

On 05 Mar 2013 07:19, Vernon Hamberg wrote:

I hope that clarifies things - again, I do understand what you are
saying, it just doesn't easily apply to this situation, so far as I
can tell.

Understood. I guess I was just having difficulty getting past both
of what I understood to be a repeated implication that the features
could not properly process UTF-16BE data because they ended up doing a
byte-by-byte conversion instead of a character conversion, and what was
an apparent attitude of "good enough for government work" with regard to
correctness. The former contrasted with my testing, and the latter
seemed incongruous with the tenor of the OP where it was stated that "we
want to be able to process Unicode text files."