On Mon, Mar 4, 2013 at 2:52 PM, Vernon Hamberg <vhamberg@xxxxxxxxxxxxxxx> wrote: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.
If you have a file saved on a Unix box or maybe a Macintosh, it'll haveMacs haven't used CR in quite some time. For all practical purposes,
only one of these, either x0D or x0A.
there are only two EOL conventions remaining: CRLF for Windows and LF
for everything else.
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!
So the typical UTF-16That is probably typical, but watch out for characters specific to
representation for our situation is ANSI characters alternating with
x00's. We also have tab characters, which end up as x05 in the PF.
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")
This mailing list archive is Copyright 1997-2013 by MIDRANGE dot 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 here. If you have questions about this, please contact