From: Whitley CTR Cecil H <WhitleyCH.ctr@cherrypoint.usmc.mil>
To: "'gentoo-accessibility@lists.gentoo.org'"
<gentoo-accessibility@lists.gentoo.org>
Subject: RE: [gentoo-accessibility] Software speech
Date: Fri, 3 Sep 2004 14:55:25 -0400 [thread overview]
Message-ID: <6D3A09C6CAB0D311BA5000902760D022040F2191@chpt0000se01.cherrypoint.usmc.mil> (raw)
[-- Attachment #1: Type: text/plain, Size: 747 bytes --]
Hi Deedra,
>you'll need speech-dispatcher speechd-up at least. Speech-dispatcher
>depends on flite I belive, so I hope you have enough ram to build it:)
I've got a gig, so that should be enough to handle pretty much anything. If
not, that'll give me the excuse i've been looking for to get another.
>Eflite is available and is in portage, but not eflite16. If you want
>eflite16 you'll have to bribe squinky86 or eradicator.
Once I get the system up and running, if you can give me any pointers, i'll
try rolling my own. I would assume modifying the eflite ebuild scripts
would be the place to start. Those are all in python aren't they? If so,
i've got enough python experience that I should be able to understand them.
Regards,
Cecil
[-- Attachment #2: Type: text/html, Size: 1345 bytes --]
next reply other threads:[~2004-09-03 18:54 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-03 18:55 Whitley CTR Cecil H [this message]
2004-09-03 18:58 ` [gentoo-accessibility] Software speech Deedra Waters
-- strict thread matches above, loose matches on Subject: below --
2004-09-09 17:39 [gentoo-accessibility] software speech Whitley CTR Cecil H
2004-09-09 17:58 ` Kenny Hitt
2004-09-09 13:56 Whitley CTR Cecil H
2004-09-09 17:04 ` Jon Hood
2004-09-09 17:12 ` Kenny Hitt
2004-09-09 17:20 ` Deedra Waters
2004-09-13 11:38 ` 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 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=6D3A09C6CAB0D311BA5000902760D022040F2191@chpt0000se01.cherrypoint.usmc.mil \
--to=whitleych.ctr@cherrypoint.usmc.mil \
--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