public inbox for blinux-list@redhat.com
 help / color / mirror / Atom feed
From: "T. V. Raman" <raman@Adobe.COM>
To: Ken Perry <whistler@blinksoft.com>
Cc: "T. V. Raman" <raman@Adobe.COM>, blinux-list@redhat.com
Subject: Re: Linux accessibility for artic
Date: Tue, 3 Dec 1996 09:56:25 -0800	[thread overview]
Message-ID: <199612031756.JAA26917@labrador> (raw)
In-Reply-To: <Pine.LNX.3.95.961202221335.22901B-100000@blinksoft.com>

Ken--

I'll answer your questions in order:

a) Dos boxes running screenreaders with dectalks may slow down if the speech
rate is set to be slow and the dos device driver continuously handshakes with
the dectalk for indexing.

emacspeak and linux perform fine with the dectalk express --I have the speech
going at 450 words a minute and it is chattering along as I work.

2) Windows NT:

I've been meaning to try this --haven't had time to write a driver for NT
--would have to be either Java or Visual Basic --since tclx does not run on NT
--select is a pretty unix-specific call --and this is what the unix driver
uses to sync with the dectalk.

This said, emacspeak should work happily on NT given the driver, but its
usefulness on that platform is questionable.

The reason why emacspeak is a complete solution on UNIX is
that  in UNIX-land X windows is meerely a graphical interface to the
underlying tools; you can write your own interface --and that is what
emacspeak does.

On NT, though emacspeak might make emacs talk, that would still not give you
access to the underlying machine or allow you to do system maintainance tasks
since all those things are inherently tied to the Windows GUI.

Finally, on the question of writing a driver;
I think the only serious attempt was by someone in Australia and he did make
considerable progress --I have now lost contact.

You might say "the proof is in the pudding" pointing at the absence of drivers
for other boxes; all I have to say is that if I had the time and motivation to
write drivers for these other boxes it would take less than a day for each
device.

-- 
Best Regards,
--raman

      Adobe Systems                 Tel: 1 (408) 536 3945   (W14-129)
      Advanced Technology Group     Fax: 1 (408) 537 4042 
      (W14 129) 345 Park Avenue     Email: raman@adobe.com 
      San Jose , CA 95110 -2704     Email:  raman@cs.cornell.edu
      http://labrador.corp.adobe.com/~raman/raman.html (Adobe  Internal)
      http://www.cs.cornell.edu/Info/People/raman/raman.html  (Cornell)
-----------------------------------------------------------------------
    Disclaimer: The opinions expressed are my own and in no way should be taken
as representative of my employer, Adobe Systems Inc.
____________________________________________________________


      reply	other threads:[~ UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Ben Van Poppel
 ` Ken Perry
   ` T. V. Raman
     ` Ken Perry
       ` T. V. Raman [this message]

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=199612031756.JAA26917@labrador \
    --to=raman@adobe.com \
    --cc=blinux-list@redhat.com \
    --cc=whistler@blinksoft.com \
    /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).