Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.lang.python > #94567 > unrolled thread

Re: Gmail eats Python

Started byJussi Piitulainen <jpiitula@ling.helsinki.fi>
First post2015-07-25 20:47 +0300
Last post2015-07-26 08:37 +0300
Articles 2 on this page of 42 — 13 participants

Back to article view | Back to comp.lang.python

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  Re: Gmail eats Python Jussi Piitulainen <jpiitula@ling.helsinki.fi> - 2015-07-25 20:47 +0300
    Re: Gmail eats Python Jussi Piitulainen <jpiitula@ling.helsinki.fi> - 2015-07-25 20:52 +0300
      Re: Gmail eats Python Laura Creighton <lac@openend.se> - 2015-07-25 20:05 +0200
        Re: Gmail eats Python Jussi Piitulainen <jpiitula@ling.helsinki.fi> - 2015-07-26 08:26 +0300
    Re: Gmail eats Python Jon Ribbens <jon+usenet@unequivocal.co.uk> - 2015-07-25 18:44 +0000
    Re: Gmail eats Python Marko Rauhamaa <marko@pacujo.net> - 2015-07-25 22:42 +0300
      Re: Gmail eats Python Ben Finney <ben+python@benfinney.id.au> - 2015-07-26 10:52 +1000
      Re: Gmail eats Python Chris Angelico <rosuav@gmail.com> - 2015-07-26 10:58 +1000
      Re: Gmail eats Python Jussi Piitulainen <jpiitula@ling.helsinki.fi> - 2015-07-26 08:01 +0300
        Re: Gmail eats Python Rustom Mody <rustompmody@gmail.com> - 2015-07-25 22:28 -0700
          Re: Gmail eats Python Chris Angelico <rosuav@gmail.com> - 2015-07-26 15:34 +1000
            Re: Gmail eats Python Rustom Mody <rustompmody@gmail.com> - 2015-07-25 23:15 -0700
              Re: Gmail eats Python Chris Angelico <rosuav@gmail.com> - 2015-07-26 16:25 +1000
                Re: Gmail eats Python Marko Rauhamaa <marko@pacujo.net> - 2015-07-26 09:55 +0300
                  Re: Gmail eats Python Rustom Mody <rustompmody@gmail.com> - 2015-07-26 01:20 -0700
                    Re: Gmail eats Python Marko Rauhamaa <marko@pacujo.net> - 2015-07-26 11:35 +0300
                      Re: Gmail eats Python Rustom Mody <rustompmody@gmail.com> - 2015-07-26 01:50 -0700
                        Re: Gmail eats Python alister <alister.nospam.ware@ntlworld.com> - 2015-07-26 09:21 +0000
                          Re: Gmail eats Python Mark Lawrence <breamoreboy@yahoo.co.uk> - 2015-07-26 12:27 +0100
                        Re: Gmail eats Python Marko Rauhamaa <marko@pacujo.net> - 2015-07-26 12:51 +0300
                          Re: Gmail eats Python Chris Angelico <rosuav@gmail.com> - 2015-07-26 20:03 +1000
                            Re: Gmail eats Python Marko Rauhamaa <marko@pacujo.net> - 2015-07-26 13:31 +0300
                            Re: Gmail eats Python Jussi Piitulainen <jpiitula@ling.helsinki.fi> - 2015-07-26 14:30 +0300
                              Re: Gmail eats Python Marko Rauhamaa <marko@pacujo.net> - 2015-07-26 14:48 +0300
                                Re: Gmail eats Python random832@fastmail.us - 2015-07-29 10:51 -0400
                                Re: Gmail eats Python Larry Martell <larry.martell@gmail.com> - 2015-07-29 10:53 -0400
                        Re: Gmail eats Python Jussi Piitulainen <jpiitula@ling.helsinki.fi> - 2015-07-26 13:43 +0300
                          Re: Gmail eats Python Rustom Mody <rustompmody@gmail.com> - 2015-07-26 06:16 -0700
                          Re: Gmail eats Python Rustom Mody <rustompmody@gmail.com> - 2015-07-28 20:35 -0700
                            Re: Gmail eats Python Laura Creighton <lac@openend.se> - 2015-07-29 18:32 +0200
                Re: Gmail eats Python Grant Edwards <invalid@invalid.invalid> - 2015-07-26 15:42 +0000
              Re: Gmail eats Python Mark Lawrence <breamoreboy@yahoo.co.uk> - 2015-07-26 12:25 +0100
          Re: Gmail eats Python Grant Edwards <invalid@invalid.invalid> - 2015-07-26 15:47 +0000
            Re: Gmail eats Python Rustom Mody <rustompmody@gmail.com> - 2015-07-26 08:59 -0700
              Re: Gmail eats Python Mark Lawrence <breamoreboy@yahoo.co.uk> - 2015-07-26 18:21 +0100
              Re: Gmail eats Python Steven D'Aprano <steve@pearwood.info> - 2015-07-27 03:40 +1000
                Re: Gmail eats Python Rustom Mody <rustompmody@gmail.com> - 2015-07-26 14:34 -0700
                Re: Gmail eats Python Chris Angelico <rosuav@gmail.com> - 2015-07-27 11:47 +1000
              Re: Gmail eats Python Grant Edwards <invalid@invalid.invalid> - 2015-07-26 19:45 +0000
                Re: Gmail eats Python Rustom Mody <rustompmody@gmail.com> - 2015-07-26 14:54 -0700
    Re: Gmail eats Python Steven D'Aprano <steve@pearwood.info> - 2015-07-26 14:49 +1000
      Re: Gmail eats Python Jussi Piitulainen <jpiitula@ling.helsinki.fi> - 2015-07-26 08:37 +0300

Page 3 of 3 — ← Prev page 1 2 [3]

#94588

FromSteven D'Aprano <steve@pearwood.info>
Date2015-07-26 14:49 +1000
Message-ID<55b466f2$0$1674$c3e8da3$5496439d@news.astraweb.com>
In reply to#94567
On Sun, 26 Jul 2015 03:47 am, Jussi Piitulainen wrote:

> Just in case anyone cares, Gnus shows me those indentations as octal
> codes, \302\240\302\240 (followed by one ASCII space). I guess a
> \302\240 is a NO-BREAK SPACE in UTF-8, and I guess Gnus does not know
> this because there is no charset specification in the headers. That
> seems to be missing whenever I see these codes instead of properly
> rendered characters and bother to check the headers.

Some of us care :-)

Zachary's post that you are referring to does have the charset declared, but
it uses individual declarations for each of the multipart/alternative
parts:


--001a1134d474c99321051bb5ef45
Content-Type: text/plain; charset=UTF-8


--001a1134d474c99321051bb5ef45
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable


On the other hand, your post sent from Gnus is lying. Despite containing
non-ASCII bytes (i.e. octal \302\240), it sends these headers:


Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 8bit


US-ASCII is 7-bit only and only defines values for ord \0 through \177 in
octal.


-- 
Steven

[toc] | [prev] | [next] | [standalone]

#94595

FromJussi Piitulainen <jpiitula@ling.helsinki.fi>
Date2015-07-26 08:37 +0300
Message-ID<lf56157eayd.fsf@ling.helsinki.fi>
In reply to#94588
Steven D'Aprano writes:

> On Sun, 26 Jul 2015 03:47 am, Jussi Piitulainen wrote:
>
>> Just in case anyone cares, Gnus shows me those indentations as octal
>> codes, \302\240\302\240 (followed by one ASCII space). I guess a
>> \302\240 is a NO-BREAK SPACE in UTF-8, and I guess Gnus does not know
>> this because there is no charset specification in the headers. That
>> seems to be missing whenever I see these codes instead of properly
>> rendered characters and bother to check the headers.
>
> Some of us care :-)

Thank you.

> On the other hand, your post sent from Gnus is lying. Despite
> containing non-ASCII bytes (i.e. octal \302\240), it sends these
> headers:
>
> Content-Type: text/plain; charset=us-ascii
> Content-Transfer-Encoding: 8bit
>
> US-ASCII is 7-bit only and only defines values for ord \0 through \177
> in octal.

Yes. Gnus made me go through a dialogue to send the message, and I
didn't understand what all the options meant. So I probably told it to
lie. My bad.

[toc] | [prev] | [standalone]

Page 3 of 3 — ← Prev page 1 2 [3]

Back to top | Article view | comp.lang.python

csiph-web