speakup, 2.6.22, and the way forward
nick at nickgawronski.com
Fri Aug 3 14:50:00 EDT 2007
Hi, there are already user space screen readers like yasr at
http://yasr.sourceforge.net that will read from the login shell as I use to
use it before I found speakup. It won't read the login messages or any
other messages but it at least has some abilities. I would also like to see
speakup continue development and support 2.6.22 and newer kernels. Why
won't they include it in the main kernel sources? It is true it has some
bugs but then don't all kernel features have bugs that get fixed from time
to time? yes. Better support for the dectalk express would be nice.
----- Original Message -----
From: "Tomas Cerha" <cerha at brailcom.org>
To: "Speakup is a screen review system for Linux." <speakup at braille.uwo.ca>
Sent: Friday, August 03, 2007 5:12 AM
Subject: Re: speakup, 2.6.22, and the way forward
> Kirk Reiser wrote:
>> I also happen to believe that a user space set of screen readers would
>> be very useful and provide users choice of the software they use. I
>> however, am not interested in writing one.
> Hello Kirk and all,
> let me just add a thought to this. I don't think that the question is
> whether there are alternatives to speakup, but whether it is possible to
> continue speakup development. And I believe most people simply want
> speakup to continue.
> I see the requirement for reading boot messages as very valid, but I
> don't think it has much to do with speakup's screen-reading
> functionality. Reading these messages is as simple as sending chunks of
> text to the synthesizer as they come. So I still see it very possible
> to reduce the kernel space code to minimum and allow future inclusion of
> speakup core within kernel and moving other parts of it into user space
> without giving up the needed functionality. Does that make sense?
> Would you, Kirk, see any problems in this approach?
> This is not only the boot messages, that we can't do in a purely
> user-space screen-reader, so we definitely need some kernel-space code,
> but the question is, whether we really need to have everything in
> kernel or only the necessary subset.
> Thank you for your attention and best regards
> Speakup mailing list
> Speakup at braille.uwo.ca
More information about the Speakup