From: Pavel Machek <pavel@ucw.cz>
To: Samuel Thibault <samuel.thibault@ens-lyon.org>,
linux-kernel@vger.kernel.org
Subject: Re: [RFC] accessibility, speakup, speech synthesis & /sys
Date: Wed, 8 Jul 2009 11:35:16 +0200 [thread overview]
Message-ID: <20090708093516.GE24385@elf.ucw.cz> (raw)
In-Reply-To: <20090701221904.GA4431@const>
On Thu 2009-07-02 00:19:04, Samuel Thibault wrote:
> Hello,
>
> Pavel Machek, le Tue 30 Jun 2009 08:34:54 +0200, a écrit :
> > > 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?
> >
> > 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.
Greg's suggestion seems ok.
> > /sys/speech ? Or even better /sys/class/speech? What is global about
> > it?
>
> As I said, there is a difference between speech synthesizers, which can
> easily be considered as devices, and screen readers (here, speakup),
> which could for instance use different synthesizers, so please don't mix
> them. Accessibility features, however, is not really a device, but as it
> was suggested it could go into the vtcon directory.
Ack.
> > 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?
> > What modifications would be needed to make useful a11y w/o additional
> > hw?
>
> It depends on what you call "useful". The desktop can already use
> software speech synthesis. When / can't be mounted, you're hosed,
> however, unless you have shipped a full software speech synthesizer in
> initrd, but even in such case the initrd script could also fail.
I'd actually prefer soft synthetiser in initrd. You know... "normal"
consoles (such as vt) do fail sometimes, too.
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
next prev parent reply other threads:[~2009-07-08 9:35 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-25 22:04 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 [this message]
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=20090708093516.GE24385@elf.ucw.cz \
--to=pavel@ucw.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=samuel.thibault@ens-lyon.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®