Re: CPYFRMIMPF and Unicode - UTF-16 in particular

Comments inline

On 3/4/2013 2:41 PM, John Yeung wrote:

On Mon, Mar 4, 2013 at 2:52 PM, Vernon Hamberg <vhamberg@xxxxxxxxxxxxxxx> wrote:

If you have a file saved on a Unix box or maybe a Macintosh, it'll have
only one of these, either x0D or x0A.

Macs haven't used CR in quite some time. For all practical purposes,
there are only two EOL conventions remaining: CRLF for Windows and LF
for everything else.

I hear you - but we don't know what is the source of these text files, so I'm just covering the bases. Besides, the *ALL in CPYFRMSTMF covers all those bases, otherwise, I believe I have to pick one.

So the typical UTF-16
representation for our situation is ANSI characters alternating with
x00's. We also have tab characters, which end up as x05 in the PF.

That is probably typical, but watch out for characters specific to
Windows-1252 which don't "fit" in one byte. These are the notorious
not-the-same-as-ISO-8859-1 characters in the (hex) range 80-9F. Most
notably, these include the Euro symbol and the angled ("smart")
quotes.

Good point, same as Scott is saying, I think. At this time, I'm told, this should not be an issue. But you know how much we get "should"-ed on!

This might be enough to say, use the IFS and transform APIs and guess at the encoding. But I'll go for this simpler route for now - now guessing, easily coded.

John