From: "Brian L. Sellden" <Brian@henge.com>
To: blinux-list@redhat.com
Cc: blinux-list@redhat.com
Subject: Re: another idea for speech.
Date: Wed, 11 Dec 1996 11:12:55 -0700 [thread overview]
Message-ID: <199612111812.LAA04444@zygote.ivory.com> (raw)
In-Reply-To: <Pine.LNX.3.95.961211124914.17454A-100000@softcon.com> (message from Travis Siegel on Wed, 11 Dec 1996 12:52:54 -0500 (EST))
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
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
HRTC
` Travis Siegel
` Brian L. Sellden
` Travis Siegel
` Joel Zimba
` William Loughborough
` Travis Siegel
` Jim Rebman
` Travis Siegel
` Brian L. Sellden [this message]
-- strict thread matches above, loose matches on Subject: below --
Travis Siegel
michael malver
Lar Kaufman
` Jim Rebman
` Jason John Griffin White
` Craig Martin
` Ken Perry
` Joel Zimba
` Ben Van Poppel
Craig Martin
` Kenneth Albanowski
` Jim Rebman
` Sam Hartman
` Kenneth Albanowski
` Steve Holmes
` Kenneth Albanowski
` Mark Newbold
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=199612111812.LAA04444@zygote.ivory.com \
--to=brian@henge.com \
--cc=blinux-list@redhat.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).