linux-kernel - Re: [RFC] accessibility, speakup, speech synthesis & /sys

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 8 Jul 2009 11:35:16 +0200
From:	Pavel Machek <pavel@....cz>
To:	Samuel Thibault <samuel.thibault@...-lyon.org>,
	linux-kernel@...r.kernel.org
Subject: Re: [RFC] accessibility, speakup, speech synthesis & /sys

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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/