NEL is defined in ISO8859-1 as code point 0x85.  In 8859-1 there are control 
characters in the range of 0x80 to 0x9f as well as 0x00 to 0x1f.  Lots of 
documentation on 8859-1 skip the control characters, so many folks don't 
realize this.

I assume that NL is short for newline.  A newline is the same thing as a 
linefeed or LF in Unix and Linux.  It is just a different name for the same 
thing.  In EBCDIC codepage 1047 there is a newline at codepoint 15 and a 
linefeed at codepoint 25.  This leads to some confusion in various conversion 
tables.  To add to the confusion z/OS Unix uses newline (15) as the end of 
line.  So if you convert linefeed to linefeed when converting from 8859-1 
things don't work.  Because of this many EBCDIC to 8859-1 conversion tables 
convert newline to linefeed, and linefeed to NEL.

Have I mentioned my intense dislike for EBCDIC before?


-----Original Message-----
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of
Alan Altmark
Sent: Wednesday, July 09, 2008 9:25 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: line end characters (was SFTP versus FTP)


On Wednesday, 07/09/2008 at 07:33 EDT, Douglas Wooster/Raleigh/[EMAIL PROTECTED]
wrote:
> Added one more line separator to the list below.  It usually burns me
> when I use iconv.
>
:
> NEL   - New/Next Line (ASCII x'85').  May see this when EBCDIC
> data is translated to ASCII, as with iconv.

NEL?  Not in any codepage I've ever heard of.  All ASCII control controls
will be 0x01-0x1F.  In order to ensure fidelity on a round trip
(EBCDIC->ASCII->EBCDIC), what you will find is that EBCDIC values that
have no ASCII equivalent will be assigned to ASCII codepoints that have no
EBCDIC equivalent.

For example, 0x85 in Windows is an ellipsis, which doesn't exist in any
EBCDIC code page.  In UNIX (ISO 8859-1) and its derivatives, it has no
meaning.  And since NL doesn't exist in ASCII, 0x15 and 0x85 can be safely
transposed.

If you found an EBCDIC codepage that *did* have an ellipsis, then the
translation for that particular codepage to Windows (1252) would have to
find some other ASCII code point to contain the NL.

Alan Altmark
z/VM Development
IBM Endicott

----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390

__________________________________________________________________________________________________

CONFIDENTIALITY NOTICE: This email from the State of California is for the sole 
use of the intended recipient and may contain confidential and privileged 
information.  Any unauthorized review or use, including disclosure or 
distribution, is prohibited.  If you are not the intended recipient, please 
contact the sender and destroy all copies of this email.  

----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390

Reply via email to