mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Samuel Thibault <samuel.thibault@ens-lyon.org>
To: linux-kernel@vger.kernel.org
Subject: [RFC] accessibility, speakup, speech synthesis & /sys
Date: Fri, 26 Jun 2009 00:04:52 +0200	[thread overview]
Message-ID: <20090625220452.GF5540@const.famille.thibault.fr> (raw)

Hello,

Just as a reminder, Speakup is an in-kernel screen reader that uses
hardware speech synthesis to say what gets printed on the Linux console.

In the process of cleaning it, we are moving its configuration stuff
into proper places.  I believe there are two things:

- per- harware speech synthesizer parameters (e.g. speed, pitch, etc.)
- screen reading parameters (e.g. characters pronunciation, key_echo,
  current synthesizer being used etc.)

Speech synthesizers should probably have their own device class, how
should it be called? "synth"? "speech"?

Synthesizers are usually plugged on serial ports, but there is no bus
abstraction for that, so I believe we can put them in the virtual bus.

Then there are the screen reading parameters. I'd tend to think that
like there are /sys/{block,firmware,fs,power}, there could be a
/sys/accessibility, or even shorter, /sys/a11y?  Speakup parameters
could then be in /sys/a11y/speakup?

Samuel

             reply	other threads:[~2009-06-25 22:05 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-25 22:04 Samuel Thibault [this message]
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
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=20090625220452.GF5540@const.famille.thibault.fr \
    --to=samuel.thibault@ens-lyon.org \
    --cc=linux-kernel@vger.kernel.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

all inboxes | Powered by JetHome®