public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: "Nick Gawronski" <nick@nickgawronski.com>
To: <speakup@braille.uwo.ca>
Subject: Re: speakup, 2.6.22, and the way forward
Date: Mon, 6 Aug 2007 13:36:01 -0600	[thread overview]
Message-ID: <000801c7d861$057c0670$270110ac@CHIHUAHUAL1> (raw)
In-Reply-To: <1186374316.8435.6.camel@taylor.homelinux.net>

Hi, yasr is a good thing but speakup I think is better as it is kernel 
based.  Bugs need to be fixed in it considering the dectalk express driver 
and other drivers probably.  I have noticed that when reading long passages 
of text using speakup the dectalk express suddenly stops reading and then I 
have to shutdown or turn off speakup then turn it back on again.  This is a 
speakup bug as in windows I am able with window eyes 6.1 to read even longer 
passages of text and don't have this stoping problem.  When do you think 
someone will look into fixing the dectalk express drivers and possibley 
others?
----- Original Message ----- 
From: "Lorenzo Taylor" <daxlinux@gmail.com>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Sent: Sunday, August 05, 2007 10:25 PM
Subject: Re: speakup, 2.6.22, and the way forward


> YASR seems to provide a pretty solid starting point for a userspace
> screen reader. All that needs to be done to make it usable early on in
> the boot process is to switch from using a virtual shell to polling the
> current console. I have talked with Mike and he seems agreeable to the
> idea, and there is even a program that seems to be able to do this in
> Solaris that is available in the CVS version. The main thing to do would
> be to attempt to port this program to Linux and other Unix-like OS's and
> then integrate it into YASR in such a way that YASR uses the console
> polling method rather than the virtual shell that it uses now. This way
> YASR can be started from init.d or a similar startup mechanism rather
> than having to be started after a speechless login. After these changes
> are made, then improvements similar to the stuff we have in Speakup can
> be added.
>
> Live long and prosper,
> Lorenzo
> On Wed, 2007-08-01 at 11:46 -0500, Travis Siegel wrote:
>> Why don't they adapt yasr or something?
>> If they want user space, that's about as user space as you can get,
>> and I'm sure Michael wouldn't mind.
>>
>>
>> _______________________________________________
>> Speakup mailing list
>> Speakup@braille.uwo.ca
>> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
> 



  parent reply	other threads:[~ UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Daniel Drake
 ` John covici
 ` John Heim
   ` Gregory Nowak
     ` John Heim
       ` Gregory Nowak
         ` Kirk Reiser
           ` Travis Siegel
             ` Lorenzo Taylor
               ` John Heim
                 ` Lorenzo Taylor
               ` Nick Gawronski [this message]
           ` Tomas Cerha
             ` Nick Gawronski
         ` John Heim
     [not found] <E1IIS12-0005G6-38@gene3.ait.iastate.edu>
 ` Nick Gawronski
   ` Gregory Nowak
     ` Nick Gawronski
       ` Gregory Nowak
     [not found]       ` <20070808142123.GA22584@gmx.net>
         ` nick
     [not found]   ` <20070808001353.GA3980@lava-net.com>
     ` Nick Gawronski
   ` Gene Collins
     ` Nick Gawronski

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='000801c7d861$057c0670$270110ac@CHIHUAHUAL1' \
    --to=nick@nickgawronski.com \
    --cc=speakup@braille.uwo.ca \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).