From mboxrd@z Thu Jan 1 00:00:00 1970 Received: (qmail 22241 invoked from network); 3 Dec 1996 17:58:58 -0000 Received: from smtp-relay-1.Adobe.COM (192.150.11.1) by mail2.redhat.com with SMTP; 3 Dec 1996 17:58:58 -0000 Received: by smtp-relay-1.Adobe.COM (8.7.5) with ESMTP id JAA29341; Tue, 3 Dec 1996 09:57:10 -0800 (PST) Received: by inner-relay-1.Adobe.COM (8.7.5) with ESMTP id JAA18187; Tue, 3 Dec 1996 09:57:38 -0800 (PST) Received: by mail-345.corp.Adobe.COM (8.7.5) with ESMTP id JAA21767; Tue, 3 Dec 1996 09:58:35 -0800 (PST) Received: by labrador (8.6.9) id JAA26917; Tue, 3 Dec 1996 09:56:25 -0800 Date: Tue, 3 Dec 1996 09:56:25 -0800 Message-Id: <199612031756.JAA26917@labrador> To: Ken Perry Cc: "T. V. Raman" , blinux-list@redhat.com Subject: Re: Linux accessibility for artic In-Reply-To: References: <199612031709.JAA26824@labrador> Reply-To: raman@Adobe.COM From: "T. V. Raman" X-Phone: 1 (408) 536-3945 X-Fax: 1(408) 537-4042 List-Id: 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. ____________________________________________________________