Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #94736
| From | random832@fastmail.us |
|---|---|
| Subject | Re: Gmail eats Python |
| Date | 2015-07-29 10:42 -0400 |
| References | <201507251634.t6PGYUvo028820@fido.openend.se> <CAKJDb-Nh6YKM5t72O2fe3Y9cKpBSg5N=s9kEtAsn7q+JHUer6w@mail.gmail.com> <201507251704.t6PH4FNx029638@fido.openend.se> <85twsrn3ob.fsf@benfinney.id.au> <CALwzidnNP-TjxND2qNh6EtxXVU7SGsRv4CNUGX1Q2fx26vuOHA@mail.gmail.com> |
| Newsgroups | comp.lang.python |
| Message-ID | <mailman.1069.1438180956.3674.python-list@python.org> (permalink) |
On Sun, Jul 26, 2015, at 02:43, Ian Kelly wrote: > What Internet standard is being violated by reflowing text content in > the message body? Well, implicitly, text is only supposed to be reflowed when format=flowed is in use, and only then when each physical line of the file ends with a space character. If there were _no_ internet standard on reflowing that would be one thing (new feature whereas the standards are behind the times), but the standard for reflowing is actually well-established (RFC 2646, dated 1999) and there's no real reason for not following it.
Back to comp.lang.python | Previous | Next | Find similar | Unroll thread
Re: Gmail eats Python random832@fastmail.us - 2015-07-29 10:42 -0400
csiph-web