Whoops! Yes, a CRLF in QP encoding without a preceding equal sign is a hard 
line break.


--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3

________________________________________
From: IBM Mainframe Assembler List <ASSEMBLER-LIST@listserv.uga.edu> on behalf 
of Charles Mills <charl...@mcn.org>
Sent: Monday, July 23, 2018 11:44 AM
To: ASSEMBLER-LIST@listserv.uga.edu
Subject: Re: Testing

In your second paragraph is the second "soft" supposed to be "hard"?

Charles


-----Original Message-----
From: IBM Mainframe Assembler List [mailto:ASSEMBLER-LIST@LISTSERV.UGA.EDU]
On Behalf Of Seymour J Metz
Sent: Monday, July 23, 2018 8:31 AM
To: ASSEMBLER-LIST@LISTSERV.UGA.EDU
Subject: Re: Testing

Okay, let me cover some basics.

An e-mail messages is a sequences of lines terminated in CRLF; the client
and server software is permitted to replace the two terminating characters
with whatever is appropriate for the OS.

A MIME part with QP (bletch!) encoding uses =CRLF for a soft break; that is,
it does not represent CRLF in the unencoded text. A CRLF not preceded by an
equal sign is a soft break; it represents a CRLF in the unencoded text.

A message with format=flowed in the Content-Transfer-Encoding header field
uses SP CR LF for a soft break and a CRLF not preceded by a space for a hard
break.

Note that the last two cases are both MIME.


--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3

________________________________________
From: IBM Mainframe Assembler List <ASSEMBLER-LIST@listserv.uga.edu> on
behalf of Paul Gilmartin <00000014e0e4a59b-dmarc-requ...@listserv.uga.edu>
Sent: Friday, July 20, 2018 1:11 PM
To: ASSEMBLER-LIST@listserv.uga.edu
Subject: Re: Testing

On 2018-07-20, at 10:26:15, Seymour J Metz wrote:

> Without format=flowed there is only CR[1], not soft CR and hard CR.
>
Are there, then, 3 different things?  Explain.

How do you classify auoted-printable's "=<CR>"?

> [1] Well, really CRLF or, in *ix, just LF, or on a really old Mac just CR.
>
Or, on z/OS, CRNL or NL.

Or, in HTML, the much-misunderstood <BR>.

-- gil

Reply via email to