From: William Hubbs <williamh@gentoo.org>
To: gentoo-accessibility@lists.gentoo.org
Subject: Re: [gentoo-accessibility] speakup on gentoo
Date: Thu, 24 Apr 2008 08:36:41 -0500 [thread overview]
Message-ID: <20080424133640.GA30440@linux1> (raw)
In-Reply-To: <1209019042.4908.19.camel@sonofthejedi.ath.cx>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi Robert,
I just did an update to the speechd-up ebuild in the tree which should
fix the issues you mentioned. The new version of speechd-up is
speechd-up-0.4-r3. Emerge this and let me know how it works for you.
On Thu, Apr 24, 2008 at 06:37:22PM +1200, Robert Grieve wrote:
> On Wed, 2008-04-23 at 23:41 -0500, William Hubbs wrote:
>
> > Speechd-up is still the way to link software speech to speakup.
> > Just do an emerge speechd-up to install the packages. The default
> > synthesizer is espeak, and it and speech dispatcher will be installed as
> > dependencies of speechd-up. Once you have everything emerged, add
> > speech-dispatcher and speechd-up to your default runlevel.
> >
> > Yes, the files that were in /proc/speakup have been moved to
> > /sys/module/speakup/parameters.
>
> In order to get this working with the new system I had to do a little
> hacking in /etc/init.d/speechdup.
>
> Specifically at top level
> SPEAKUPDIR=/sys/module/speakup/parameters # Not /proc/speakup
>
> and in load_speakup()
>
> echo soft > ${SPEAKUPDIR}/synth #which used to read echo sftsyn
>
> I have no idea how, but people who want this to work for kernels
> >=gentoo-sources-2.6.25-r1 need these in /etc/init.d/speechd-up,
> and people who want the pre 2.6.25 need the way it is as of this morning
> Which had the following at the top if it helps.
>
> $Header: /var/cvsroot/gentoo-x86/app-accessibility/speechd-up/files/speechd-up.rc,v 1.6 2007/05/30 04:05:27 williamh Exp $
>
> Hope this is more helpful than annoying.
> Best,
> Robert
- --
William Hubbs
gentoo accessibility team lead
williamh@gentoo.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (GNU/Linux)
iEYEARECAAYFAkgQjOgACgkQblQW9DDEZTh4xwCdENzQnhs4DWpCSLgdyfmo74CE
xGcAnjIfolG50+gL5JtCYecshAI/0zcY
=mPhe
-----END PGP SIGNATURE-----
--
gentoo-accessibility@lists.gentoo.org mailing list
prev parent reply other threads:[~2008-04-24 13:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-19 21:54 [gentoo-accessibility] speakup on gentoo William Hubbs
2008-04-23 9:22 ` Robert Grieve
2008-04-23 13:05 ` William Hubbs
2008-04-24 3:07 ` Robert Grieve
2008-04-24 4:41 ` William Hubbs
2008-04-24 6:37 ` Robert Grieve
2008-04-24 13:36 ` William Hubbs [this message]
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=20080424133640.GA30440@linux1 \
--to=williamh@gentoo.org \
--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