From: "T. V. Raman" <raman@Adobe.COM>
To: blinux-list@redhat.com
Subject: Re: Got some questions?
Date: Tue, 3 Dec 1996 15:29:54 -0800 [thread overview]
Message-ID: <199612032329.PAA28307@labrador> (raw)
In-Reply-To: <Pine.LNX.3.95.961203041822.30041A-100000@blinksoft.com>
Ken Perry writes:
>
>As for the device driver for Emacs speak the
> only speach access software out there you have to right that driver in
> emacs as far as I understand it. If it was as simple as writing it in C
Ken-- you clearly *dont* understand it.
The device driver for emacspeak is written in TCL --not in "emacs" as you put
it.
And the reason why emacspeak is so portable is specifically because of the
above; the driver runs stably on every platform that runs TCL.
> or C++ I think there would be one writen. As it is right now if you don't
> have Dectalk you don't have speech. There is a nice braille term program
> if you have a braille display. I hear the people who wrote the braille
> screen reader were thinking about writing a speech out put but then I have
> seen nothing of that since I wrote them about 6 months ago.
>
> Ken /whistler
>
>
> On Tue, 3 Dec 1996, Jim Corbett wrote:
>
> > Hello there,
> >
> > I have been monitoring this list for five months and I am inpressed with the
> > caliber of the discussions.
> >
> > So now I feel comfortable enough to toss my hat into the ring and post a few
> > questions.
> >
> > My experiences with Linux or Unix has come from the Net or through the
> > college I work for. However this experience has come via a terminal emulator.
> >
> > I have been thinking about setting up a computer at home to play with Linux.
> > I don't really want to tie up my P166, so I was thinking of using a 286 or a
> > 386 that I can pick up rather ceap these days. Any ideas?
> >
> > Also what should I be considering for a synthesizer? I have the means of
> > accessing a multitude of internal or external devices. ie. acsent pc,
> > acsent sa, Artic 215, 615, or a Echo internal card.
> >
> > The latest discussion in regards to Artic, does cause me some concern.
> >
> > I am currently in my third year of Information systems, and have enough
> > experience with Assembler and C plus plus to try and tackcle writing a
> > device driver. so if any one out there has the source code for a driver, I
> > would be more than greatful to have it.
> >
> > Many thanks in advance,
> >
> > Jim corbett
> > BLINDNET@reach.net
> >
> > Jim Corbett
> > BLINDNET@reach.net
> >
> > ---
> > 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: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
Jim Corbett
` Ken Perry
` T. V. Raman [this message]
le big mac
` Ken Perry
` Travis Siegel
` Luke Davis
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=199612032329.PAA28307@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).