public inbox for blinux-list@redhat.com
 help / color / mirror / Atom feed
From: jrebman@netcom.com (Jim Rebman)
To: blinux-list@redhat.com
Subject: Re: another idea for speech.
Date: Wed, 11 Dec 1996 09:22:56 -0800 (PST)	[thread overview]
Message-ID: <199612111722.JAA28788@netcom16.netcom.com> (raw)
In-Reply-To: <Pine.LNX.3.95.961211124914.17454A-100000@softcon.com> from "Travis Siegel" at Dec 11, 96 12:52:54 pm

> legitimate question.  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.  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?


Last time for the PCWM...

NO, NO, NO!  Emacspeak is not for X-Windows -- it is for just what you 
describe; native speech access for the linux/unix console and shell 
users.  It is possible to run it in an xterm window though.  I have no 
idea of how to do this because I am not running X yet, but Raman has used 
it in this manner.  So, now you can stop ignoring Emacspeak and start 
investigating how you can put it to work for you.  Here are a couple of 
hints:

You can find Emacspeak at 
www.cs.cornell.edu/Info/People/raman/emacspeak/emacspeak.html

If you do not have a dectalk express, or other serial dectalk, or an 
Alpha running the software dectalk, then you will have to write your own 
driver for your synthesizer.

The driver will have to be written in tclx (extended tcl), not in "Emacs" 
or Emacs-lisp, or assembler, or pascal, or c, or ...

Yes, there will be some work involved, and as Raman has pointed out, it 
is not too difficult, and as he has also pointed out, in this world of 
free software, there is a give and take process involved -- you take the 
Emacspeak, you write a driver for it, and you give the driver back to the 
community at large.  So now, please stop fretting about the absence of 
native speech for linux/unix -- it does exist, but it might require some 
effort to make it work.  I am running it on a pentium-166 tower machine 
with no terminal attached, and on a pentium-133 laptop.  Trust me, it 
does actually provide speech for linux.

-- JR


  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 [this message]
         ` Travis Siegel
       ` Brian L. Sellden
  -- 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=199612111722.JAA28788@netcom16.netcom.com \
    --to=jrebman@netcom.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).