Not much help but the going work-around is to not use the webmail
interface for this and use mutt, thunderbird, etc. via imap and smtp.
The added advantage there is you can add extensions to linkify bugs
and such for places like launchpad, bugzilla, etc..
J
--
On Wed, Mar 21, 2012 at 9:55 AM, Dave Martin <dave.martin@linaro.org> wrote:
> Hi all,
>
> Does anybody know how to stop the Gmail webmail frontend from corrupting sequences of space characters in preformatted text?
>
> When replying to a plaintext mail, Gmail seems to turn every second space into an ISO8859-1/Unicode non-breaking space character (U00A0). This seems to be a workaround for broken mail readers which would incorrectly collapse spaces in implicitly fixed-format text in received messages. Unfortunately, it's also an effective workaround for correct behaviour by properly-implemented mail clients. Direct replies via SMTP to smtp.googlemail.com don't get destroyed in this way, unless a broken client is used is used to generate the reply.
>
> This seems to be the cause behind patch discussion threads turning, sooner or later, into a mass of ? characters (this is what some agents like Mutt squash non-ascii characters to when quoting the original message in ascii plaintext replies -- this compounds the problem but is not the root cause -- the text is already badly damaged by this stage).
>
> See:
> * http://www.ieft.org/rfc/rfc2646.txt
> * http://lists.luv.asn.au/pipermail/luv-main/2011-November/000580.html
>
>
> Apart from "never reply to patches via webmail", does anyone know a workaround?
>
> Cheers
> ---Dave
>
> ----- Forwarded message from Dave Martin <dave.martin@linaro.org> -----
>
> MIME-Version: 1.0
> Received: by 10.52.19.176 with HTTP; Wed, 21 Mar 2012 08:31:28 -0700 (PDT)
> In-Reply-To: <20120321153006.GA2064@linaro.org>
> References: <20120321153006.GA2064@linaro.org>
> Date: Wed, 21 Mar 2012 15:31:28 +0000
> Delivered-To: dave.martin@linaro.org
> Message-ID: <CA+wbFdezDj3J8zsUMjZ4bky6C6dHdGJVnAwxFDfiN7-JKrsPdA@mail.gmail.com>
> Subject: Re: Gmail test
> From: Dave Martin <dave.martin@linaro.org>
> To: Dave Martin <dave.martin@linaro.org>
> Content-Type: text/plain; charset=ISO-8859-1
> Content-Transfer-Encoding: quoted-printable
>
> Can Gmail do it ... ??
> Come on!
>
> On Wed, Mar 21, 2012 at 3:30 PM, Dave Martin <dave.martin@linaro.org> wrote:
>> two spaces
>>
>> preformatted
>> text
>> is a pain
>
>
>
> --
> Dave Martin <dave.martin@linaro.org>
> Linaro Kernel Working Group
>
> --
> http://www.linaro.org/ -- Open source software for ARM SoCs
>
> http://www.facebook.com/pages/Linaro
> http://twitter.com/#!/linaroorg
> http://www.linaro.org/linaro-blog/
>
> ----- End forwarded message -----
>
> _______________________________________________
> linaro-dev mailing list
> linaro-dev@lists.linaro.org
> http://lists.linaro.org/mailman/listinfo/linaro-dev
Joey STANFORD
Engineering Program Manager
Office: +1-303-800-6609
http://www.linaro.org/
Open source software for ARM SoCs
_______________________________________________
linaro-dev mailing list
linaro-dev@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-dev
Amber Graner
User Experience and Community Specialist
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog