From: Kenny Hitt <kenny@hittsjunk.net>
To: gentoo-accessibility@lists.gentoo.org
Subject: Re: [gentoo-accessibility] software speech
Date: Thu, 9 Sep 2004 12:12:17 -0500 [thread overview]
Message-ID: <20040909171216.GA11182@blackbox> (raw)
In-Reply-To: <1094749486.9873.5.camel@localhost>
I'm interested. Where do I go and what to I do? One good thing about
using speakup for a long time is I have a hardware synth, so breaking
software speech could be fun.
Kenny
On Thu, Sep 09, 2004 at 12:04:48PM -0500, Jon Hood wrote:
> Cecil,
> Please do report back on your findings. Also, if you have some time and
> patience and have no fear of breaking things, I may get you to test out
> a speech-dispatcher 5.0 ebuild. It has some problems right now so it's
> not in portage, and I've had power outages due to the storms/hurricanes,
> but send me an email if you're brave! That goes to anyone on list who
> wants to break...er...update their systems with these packages :).
> -Jon
>
> On Thu, 2004-09-09 at 08:56, Whitley CTR Cecil H wrote:
> > Okay, i'll track it down and i'll post here in either case.
> > Thanks,
> > Cecil
--
gentoo-accessibility@gentoo.org mailing list
next prev parent reply other threads:[~2004-09-09 17:12 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-09 13:56 [gentoo-accessibility] software speech Whitley CTR Cecil H
2004-09-09 17:04 ` Jon Hood
2004-09-09 17:12 ` Kenny Hitt [this message]
2004-09-09 17:20 ` Deedra Waters
2004-09-13 11:38 ` Kenny Hitt
-- strict thread matches above, loose matches on Subject: below --
2004-09-09 17:39 Whitley CTR Cecil H
2004-09-09 17:58 ` Kenny Hitt
2004-09-09 12:14 Whitley CTR Cecil H
2004-09-09 12:16 ` Deedra Waters
2004-09-07 12:25 [gentoo-accessibility] Software speech Whitley CTR Cecil H
2004-09-03 18:55 Whitley CTR Cecil H
2004-09-03 18:58 ` Deedra Waters
2004-09-03 17:52 Whitley CTR Cecil H
2004-09-03 18:20 ` Deedra Waters
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=20040909171216.GA11182@blackbox \
--to=kenny@hittsjunk.net \
--cc=gentoo-accessibility@lists.gentoo.org \
/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