The traditional separator was CRLF, but the Multics developers decide to use a
single character, and Unix followed suit; I don't know why they didn't choose
RS ('1E'X) which, IMHO, would have been a much more sensible choice. Maybe the
wanted to support multi-line messages?
--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3
________________________________________
From: IBM Mainframe Discussion List [[email protected]] on behalf of
Paul Gilmartin [[email protected]]
Sent: Wednesday, July 28, 2021 9:44 AM
To: [email protected]
Subject: Re: FTP distributed system EBCDIC encoded file
On Wed, 28 Jul 2021 12:29:22 +0000, Seymour J Metz wrote:
> ...
>For historical reasons, Unix misused the Line Feed (LF) character as a logical
>new line ...
>
For similar bad historical reasons, z/OS iconv (and UNICODE services generally?)
mistranslates ASCII* LF<->NL EBCDIC, causing compatibility problems.
>Does anybody know whether Unix System Services uses LF or NEL as a logical new
>line for files tagged as UTF-8?
>
I'd expect the answer to be the same as for files taggeed ISO-8859-x: UNIX or
DOS-think.
Should 819 differ from 1252 in that respect?
-- gil
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
