linux-kernel - [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-next>] [day] [month] [year] [list]

Date:	Fri, 26 Jun 2009 00:04:52 +0200
From:	Samuel Thibault <samuel.thibault@...-lyon.org>
To:	linux-kernel@...r.kernel.org
Subject: [RFC] accessibility, speakup, speech synthesis & /sys

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