public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Samuel Thibault <samuel.thibault@ens-lyon.org>
To: Pavel Machek <pavel@ucw.cz>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [RFC] accessibility, speakup, speech synthesis & /sys
Date: Sun, 12 Jul 2009 10:57:02 -0400	[thread overview]
Message-ID: <20090712145702.GA4703@const> (raw)
In-Reply-To: <20090712103133.GE2033@elf.ucw.cz>

Pavel Machek, le Sun 12 Jul 2009 12:31:34 +0200, a écrit :
> On Wed 2009-07-08 11:42:19, Samuel Thibault wrote:
> > Pavel Machek, le Wed 08 Jul 2009 11:35:16 +0200, a écrit :
> > > On Thu 2009-07-02 00:19:04, Samuel Thibault wrote:
> > > > Pavel Machek, le Tue 30 Jun 2009 08:34:54 +0200, a écrit :
> > > > > Please keep a11y and similar madness far from kernel.
> > > > 
> > > > What do you qualify as "madness" precisely?  Could you explain why you
> > > > are using such extreme word?
> > > 
> > > If the word is so long that you have to write number of its letters
> > > inside... then you are using wrong word.
> > 
> > Unfortunately that's the word.  If the very notion of accessibility was
> > realized by mankind earlier maybe we'd have had a shorter word for it.
> 
> "speech" would seem good enough substitute.

For the speech case. Then you could have braille, speech recognition,
etc.

> > > > > BTW... from 486+, cpus are fast enough for speech synthesis. Why not
> > > > > doing it in software, viewing hw synthetisers as 'flite coprocessors'?
> > > > 
> > > > At least because flite is very far from proprietary hardware
> > > > synthesizers in terms of quality.
> > > 
> > > Well... but for reading boot messages, it might be adequate, right?
> > 
> > I'd actually say it's particularly not adequate.  Try to feed your dmesg
> > to a speech synthesizer and try to understand it.
> 
> Do you really expect blind people to do kernel hacking?

They do.  Why shouldn't they be able to?

> > > You know... "normal" consoles (such as vt) do fail sometimes, too.
> > 
> > Yes, and in such case sighted and blind users are on equal basis.  In
> > that case there is no need for a particular support for blind people.
> 
> You know, we do not translate kernel messages into other languages,
> either. So maybe we should make sure that Linux machines can be used
> without reading dmesg, and just do it from initrd?

People can learn english. Blind people can't learn seeing.

> After all, most distributions _already_ put splashscreens on, so 99%
> of people do not see kernel messages, either...

Blindness is orthogonal to that 99%.

Samuel

  reply	other threads:[~2009-07-12 14:57 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-25 22:04 [RFC] accessibility, speakup, speech synthesis & /sys Samuel Thibault
2009-06-30  4:18 ` Greg KH
2009-06-30 13:08   ` Samuel Thibault
2009-06-30 15:34     ` Greg KH
2009-06-30 20:01       ` Samuel Thibault
2009-06-30  6:34 ` Pavel Machek
2009-07-01 22:19   ` Samuel Thibault
2009-07-08  9:35     ` Pavel Machek
2009-07-08  9:42       ` Samuel Thibault
2009-07-12 10:31         ` Pavel Machek
2009-07-12 14:57           ` Samuel Thibault [this message]
2009-07-14  9:52             ` Pavel Machek
2009-07-14 12:44               ` Samuel Thibault
2009-07-19 21:27                 ` Pavel Machek

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=20090712145702.GA4703@const \
    --to=samuel.thibault@ens-lyon.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@ucw.cz \
    /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