Bob Kline wrote:
>
>I just noticed that the following passage in RFC 822:
For future interest, RFC 822 has LONG since been replaced, first by RFC
2822, then by RFC 5322. I believe the white space folding requirement is
still there, but something that violates 822 but not 5322 (and there are
seve
On Jan 20, 9:58 am, Dennis Lee Bieber wrote:
> On Thu, 20 Jan 2011 10:08:40 -0500, Bob Kline
> declaimed the following in gmane.comp.python.general:
>
>
>
> > I just noticed that the following passage in RFC 822:
>
> > The process of moving from this folded multiple-line
> >
On Jan 20, 9:55 am, Bob Kline wrote:
> On 1/20/2011 12:23 PM, Carl Banks wrote:
>
>
>
> > On Jan 20, 7:08 am, Bob Kline wrote:
> >> I just noticed that the following passage in RFC 822:
>
> >> The process of moving from this folded multiple-line
> >> representation of a
On Thu, 20 Jan 2011 17:58:36 -0500, Bob Kline wrote:
> Thanks. I'm not sure everyone would agree that it's OK to collapse
> multiple consecutive spaces into one, but I'm beginning to suspect that
> those more concerned with preserving as much as possible of the original
> message are in the mino
On 1/20/2011 5:34 PM, Martin Gregorie wrote:
On Thu, 20 Jan 2011 16:25:52 -0500, Bob Kline wrote:
On 1/20/2011 3:48 PM, Martin Gregorie wrote:
That's only a problem if your code cares about the composition of the
whitespace and this, IMO is incorrect behaviour. When the separator
between synta
On Thu, 20 Jan 2011 16:25:52 -0500, Bob Kline wrote:
> On 1/20/2011 3:48 PM, Martin Gregorie wrote:
>> That's only a problem if your code cares about the composition of the
>> whitespace and this, IMO is incorrect behaviour. When the separator
>> between syntactic elements in a header is 'whitespa
On 1/20/2011 3:48 PM, Martin Gregorie wrote:
That's only a problem if your code cares about the composition of the
whitespace and this, IMO is incorrect behaviour. When the separator
between syntactic elements in a header is 'whitespace' it should not
matter what combination of newlines, tabs and
On Thu, 20 Jan 2011 12:55:44 -0500, Bob Kline wrote:
> On 1/20/2011 12:23 PM, Carl Banks wrote:
>> On Jan 20, 7:08 am, Bob Kline wrote:
>>> I just noticed that the following passage in RFC 822:
>>>
>>> The process of moving from this folded multiple-line
>>> representatio
On 1/20/2011 12:58 PM, Dennis Lee Bieber wrote:
I'd first be concerned about the absence of the line ending sequence
specified by the RFC: carriage return (CR; \r) followed by line feed
(LF; \n).
I realized after I posted the original message that this might distract
from the issue I'
On 1/20/2011 12:23 PM, Carl Banks wrote:
On Jan 20, 7:08 am, Bob Kline wrote:
I just noticed that the following passage in RFC 822:
The process of moving from this folded multiple-line
representation of a header field to its single line represen-
tation is c
On Jan 20, 7:08 am, Bob Kline wrote:
> I just noticed that the following passage in RFC 822:
>
> The process of moving from this folded multiple-line
> representation of a header field to its single line represen-
> tation is called "unfolding". Unfolding is acc
I just noticed that the following passage in RFC 822:
The process of moving from this folded multiple-line
representation of a header field to its single line represen-
tation is called "unfolding". Unfolding is accomplished by
regarding CRLF immediat
12 matches
Mail list logo
