From: "T. V. Raman" <raman@Adobe.COM>
To: blinux-list@redhat.com
Subject: Re: Linux accessibility for artic
Date: Tue, 3 Dec 1996 09:09:02 -0800 [thread overview]
Message-ID: <199612031709.JAA26824@labrador> (raw)
In-Reply-To: <Pine.LNX.3.95.961202213342.18865B-100000@blinksoft.com>
Ken Perry writes:
>
> out there are the braille terminal and emacs speak. I hear a few people
> are trying to make emacs speak work for some of the more affordable
> synthisisers but I have looked through that code and since the writer of
> Emacs speak has made it for Dec talk using the voices it is not as easy a
> task as would be hoped. If you happen to find something out there that I
The above statement --"the author of emacspeak has made it dectalk voices
specific" is grossly untrue
Emacspeak does provide aural syntax coloring using Dectalk voices if you
happen to have a dectalk, but this is a user toggle that can be turned on
and off.
And though the author of the note I am following up to chooses to say "I have
looked through that code ..."
I bet you that anyone who is motivated enough to develop a driver for other
synthesizers would be able to develop a voice locking module for other speech
boxes if he/she so chooses.
In the free software world, things never happen if one just chooses to ask for
things; one has to be prepared to give as well.
> have missed though please let me know cause like you there is no way I am
> going to buy a dec talk at that price.
>
> Ken /whistler
>
> On Tue, 3 Dec 1996, Ben Van Poppel wrote:
>
> > I haven't actually got Linux yet but I thought I'd better start
> > researching. I have only found one voice access program for Linux, that
> > being Emacspeak. However, I haven't the resources to by a DecTalk
> > synthesizer and a terminal system doesn't appeal to me either. Are there
> > any voice access systems for Linux that can use Artic, either TransPort
> > or Double Talk speech synthesizers?
> >
> >
> > ---
> > Send your message for blinux-list to blinux-list@redhat.com
> > Blinux software archive at ftp://leb.net/pub/blinux
> > Blinux web page at http://leb.net/blinux
> > To unsubscribe send mail to blinux-list-request@redhat.com
> > with subject line: unsubscribe
> >
>
> ---
> Send your message for blinux-list to blinux-list@redhat.com
> Blinux software archive at ftp://leb.net/pub/blinux
> Blinux web page at http://leb.net/blinux
> To unsubscribe send mail to blinux-list-request@redhat.com
> with subject line: unsubscribe
--
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.
____________________________________________________________
next prev parent 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 [this message]
` Ken Perry
` T. V. Raman
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=199612031709.JAA26824@labrador \
--to=raman@adobe.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).