[lkml]   [2009]   [Jul]   [1]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [RFC] accessibility, speakup, speech synthesis & /sys

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?

> /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.

> 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.

> 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.

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2009-07-02 00:59    [W:0.113 / U:0.816 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site