From: Geetha Shamanna <s_geetha@vsnl.com>
To: blinux-list@redhat.com
Subject: Re: Speakup questions
Date: Thu, 15 Aug 2002 01:07:47 +0500 [thread overview]
Message-ID: <3.0.5.32.20020815010747.0081e830@bgl.vsnl.net.in> (raw)
In-Reply-To: <15706.43278.678702.471906@localhost.localdomain>
I plan to use the same internal synthesizer for both Speakup and Emacspeak
(DoubleTalk PC internal). Is that likely to cause problems?
Geetha
At 03:01 PM 14/08/02 -0400, you wrote:
>
>Hello,
>
>I think the default key assignments file is in the "doc" subdirectory
>of the "speakup"speakup" directory that results from unpacking the
>archive. It's also on the speakup web site.
>
>
>Speakup and emacspeak can coexist, unless you use the same external
>synthesizer for both. In general, when I wish to use emacspeak, I
>boot a kernel image that does not start speakup. I have, however, had
>both running, where emacspeak uses Viavoice Outloud as its synth, and
>speakup is using my doubletalk lt.
>
>-Dave
>
>
>
>
>_______________________________________________
>Blinux-list mailing list
>Blinux-list@redhat.com
>https://listman.redhat.com/mailman/listinfo/blinux-list
>
>
>
>---
>Incoming mail is certified Virus Free.
>Checked by AVG anti-virus system (http://www.grisoft.com).
>Version: 6.0.381 / Virus Database: 214 - Release Date: 02/08/02
>
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
Geetha Shamanna
` Janina Sajka
` Dave Hunt <
` Geetha Shamanna [this message]
` Dave Hunt <
` Janina Sajka
` Geetha Shamanna
` Janina Sajka
[not found] ` <Pine.LNX.4.44.0208141404080.26724-100000@TekRD.grg.afb.net >
` Geetha Shamanna
` Janina Sajka
` ADFM
` John
` Janina Sajka
` John
` Jude DaShiell
` David Csercsics
` John
` Pawel (Paul) Loba
` Janina Sajka
` Janina Sajka
[not found] ` <Pine.LNX.4.44.0208141607110.26724-100000@TekRD.grg.afb.net >
` Geetha Shamanna
-- strict thread matches above, loose matches on Subject: below --
speakup questions Kristoffer Gustafsson
` Buddy Brannan
` Kirk Reiser
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=3.0.5.32.20020815010747.0081e830@bgl.vsnl.net.in \
--to=s_geetha@vsnl.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).