public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: Corinna Vinschen <vinschen@redhat.com>
To: overseers@sourceware.org
Subject: Re: Could we start accepting rich-text postings on the gcc lists?
Date: Sat, 24 Nov 2012 17:14:00 -0000	[thread overview]
Message-ID: <20121124100816.GB17347@calimero.vinschen.de> (raw)
In-Reply-To: <CAD_=9DT40_1VJopMk+OuRv450hzL3hnVbw-wKpX8Up-quL0XKg@mail.gmail.com>

On Nov 23 16:18, Diego Novillo wrote:
> On Fri, Nov 23, 2012 at 4:08 PM, Jonathan Larmour <jifl@jifvik.org> wrote:
> 
> > Maybe something can be done to deal with these, but it may be that that
> > would involve so many compromises that keeping things as plain text only
> > might still be "least worst".
> 
> Thanks.  I'm actually surprised that we have all these problems with
> html e-mail, when just about every other development community seems
> to cope with it without ill side-effects.

There appears to be an unspoken agreement between the HTML email
advocates that these days *everybody* is using a HTML capable MUA.
This is just not true.  I'm using mutt and I'm sure I'm not the only
one being more comfortable using a simple terminal based MUA than one
of these shine but (IMHO) unusable GUI MUAs.

Also, for visually impaired users a text mail has the advantage to be
the simpler and least error-prone input for a braille display or a
narrator.  If you use styles and stuff and fluff, you don't add any
input which can't also be put into plain text, but you create harder to
understand mails.

Text mails are readable by *everyone*, even impaired users.  It's the
lowest common denominator everyone can agree upon and use without
trouble.  Therefore, from a practical and usability point of view, it's
much preferred over HTML mail.


Corinna

-- 
Corinna Vinschen
Cygwin Project Co-Leader
Red Hat

  parent reply	other threads:[~2012-11-24 10:08 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-23 20:12 Diego Novillo
2012-11-23 20:14 ` Andrew Pinski
2012-11-23 20:24   ` Ruben Safir
2012-11-23 20:29     ` Diego Novillo
2012-11-23 20:35       ` Ruben Safir
2012-11-23 20:40         ` Diego Novillo
2012-11-23 21:08           ` Ruben Safir
2012-11-23 20:32   ` Diego Novillo
2012-11-23 20:36     ` Ruben Safir
2012-11-24 17:47     ` Ian Lance Taylor
2012-11-24 17:48       ` Robert Dewar
2012-11-24 18:08         ` Daniel Berlin
2012-11-24 18:10           ` Robert Dewar
2012-11-25 15:24             ` Richard Biener
2012-11-25  1:53           ` Ruben Safir
2012-11-24 18:29         ` Jonathan Wakely
2012-11-24 19:43           ` Robert Dewar
2012-11-25 13:58         ` Richard Biener
2012-11-24 17:59       ` Daniel Berlin
2012-11-24 18:13         ` Frank Ch. Eigler
2012-11-24 19:46         ` Ruben Safir
2012-11-25  1:56           ` Daniel Berlin
2012-11-25 13:56         ` Jonathan Larmour
2012-11-25 19:44           ` Diego Novillo
2012-11-26 23:18       ` Gabriel Dos Reis
2012-11-24 10:08   ` Robert Dewar
2012-11-23 21:19 ` Jonathan Larmour
2012-11-23 21:21   ` Diego Novillo
2012-11-23 21:52     ` Paolo Carlini
2012-11-23 23:44     ` Per Bothner
2012-11-24 17:14     ` Corinna Vinschen [this message]
2012-11-24 17:57       ` Daniel Berlin
2012-11-24 17:58         ` Daniel Berlin

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20121124100816.GB17347@calimero.vinschen.de \
    --to=vinschen@redhat.com \
    --cc=overseers@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).