Re: [luv-main] Debian OEM mode install without preseeding ?
On Wed, Nov 16, 2011 at 13:01, Trent W. Buck <trentbuck@gmail.com> wrote:
PS: your stupid MUA appears to be replacing every SECOND space in multi-space sequences to a non-breaking space, which is fucking stupid. You're (implicitly) using format=fixed (ref. RFC2646), so the shitty workarounds to get preformatted text in format=flowed are neither necessary nor desirable. Rant, rage, grumble, bitch, moan.
Hmm, I'm using the gmail web interface. Do you see the same problem with email sent by other people using the gmail web interface? (wondering if it's a setting or lab setting I can play with). Marcus. -- Marcus Furlong
Marcus Furlong wrote:
On Wed, Nov 16, 2011 at 13:01, Trent W. Buck <trentbuck@gmail.com> wrote:
PS: your stupid MUA appears to be replacing every SECOND space in multi-space sequences to a non-breaking space, which is fucking stupid. You're (implicitly) using format=fixed (ref. RFC2646), so the shitty workarounds to get preformatted text in format=flowed are neither necessary nor desirable. Rant, rage, grumble, bitch, moan.
Hmm, I'm using the gmail web interface. Do you see the same problem with email sent by other people using the gmail web interface? (wondering if it's a setting or lab setting I can play with).
TBH, I don't know. I see it from time to time without really registering it; this time I just happened to snap.
On 16.11.11 14:12, Trent W. Buck wrote:
Marcus Furlong wrote:
On Wed, Nov 16, 2011 at 13:01, Trent W. Buck <trentbuck@gmail.com> wrote:
PS: your stupid MUA appears to be replacing every SECOND space in multi-space sequences to a non-breaking space, which is fucking stupid. You're (implicitly) using format=fixed (ref. RFC2646), so the shitty workarounds to get preformatted text in format=flowed are neither necessary nor desirable. Rant, rage, grumble, bitch, moan.
Hmm, I'm using the gmail web interface. Do you see the same problem with email sent by other people using the gmail web interface? (wondering if it's a setting or lab setting I can play with).
TBH, I don't know. I see it from time to time without really registering it; this time I just happened to snap.
The "problem" post looked OK here, handled fine by mutt, with none of those whacko "=Ax" codes. Looking at the raw email was unrevealing, since it was "Content-Transfer-Encoding: base64" I've just assumed that all that "=Ax" gobbeldygook is raw M$, and therefore essentially incurable at source. At one stage, I had vim mappings to fix the three most common encryptions, but it is now so long since I last received any offending text. Erik -- Anything can be impossible, given sufficient bureaucracy.
On 16 November 2011 20:00, Erik Christiansen <dvalin@internode.on.net> wrote:
The "problem" post looked OK here, handled fine by mutt, with none of those whacko "=Ax" codes.
That is standard QP encoding http://en.wikipedia.org/wiki/Quoted-printable AFAIK nobody here is complaining about the use of QP or BASE64, that is just something that is required for non-ASCII characters. Like the non-breakable-space being discussed here. -- Brian May <brian@microcomaustralia.com.au>
participants (4)
-
Brian May -
Erik Christiansen -
Marcus Furlong -
Trent W. Buck