From mboxrd@z Thu Jan 1 00:00:00 1970 Received: (qmail 28442 invoked from network); 11 Dec 1996 18:18:13 -0000 Received: from ppp118.henge.com (HELO zygote.ivory.com) (204.144.151.177) by mail2.redhat.com with SMTP; 11 Dec 1996 18:18:12 -0000 Received: (from brian@localhost) by zygote.ivory.com (8.7.6/8.7.3) id LAA04444; Wed, 11 Dec 1996 11:12:55 -0700 Date: Wed, 11 Dec 1996 11:12:55 -0700 Message-Id: <199612111812.LAA04444@zygote.ivory.com> From: "Brian L. Sellden" To: blinux-list@redhat.com CC: blinux-list@redhat.com In-reply-to: (message from Travis Siegel on Wed, 11 Dec 1996 12:52:54 -0500 (EST)) Subject: Re: another idea for speech. Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII List-Id: Hi folks, > > I am getting weary of posts like this. Linux access > > comes in many different forms. A console screen reader is only > > one of them. Travis, whether or not you 'give a fiddle' > > about X Windows access is of concern to noone. > > On this list, discussions will continue on several different topics. > > Getting access to consoles, X Windows, ttys, are all legitimate > > topics. > I have no problem with folks using x, neither do I think that console > access only is the answer. Don't start jumping on me for asking a > legitimate question. Ok, let's get the facts straight. You answered a post about X Windows access by stating that you didn't care about X Windows access, that you only care about access to the console, and what does the world have for *me*. I don't think that posts that state "Who cares what *you* want, what about *me*!" are particularly productive. The original poster was not talking about access to the console! > As of yet, there is nothing (I repeat) nothing for > just plain shell/console users of linux to give us speech access. That is > what I wanted, and that is what my question was. Now if you think that's > boring, that's fine, but I (and several others I know) would welcome such > a thing. Nobody thinks access to the console is boring. Replying to a post about GUI access with your question about console access *is* boring. > Emacspeak is for x-windows, what is there for normal shell > users? The answer is nothing. Now by your own words, let's keep as many > discussions going as possible. Well, this is one of those discussions. > Now, as I asked before, does anyone have any ideas on how this could be > done? Travis, here's a little PCWM for you. Emacspeak is *not* an X Windows screen-reader. The author, Dr. T. V. Raman, is on this list, and has explained this in great detail several times on this list. *PLEASE* do some research! In a nut-shell, emacspeak runs wherever emacs runs - from the console *or* in an X Windows session. Most people on this list who don't use emacspeak don't do so because Dr. Raman hasn't written a driver for their particular synthesizer. Dr. Raman has stated that he has no need to write drivers for other cards, and that doing so is not difficult. So, Travis, the easy answer is for you to learn TCLX, a rather small interpreted language, and write yourself a driver. Then, you can give it to others with the same synth. Wouldn't that be great? Regards, Brian. -- --------------- Brian L. Sellden - brian@henge.com, brians@usa.net User of Emacspeak 5.0, making Unix talk. http://www.henge.com/~brian