From: Tyler Spivey <tspivey@pcdesk.net>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: grml spelling issues
Date: Sun, 18 Mar 2007 16:16:13 -0700 [thread overview]
Message-ID: <20070318231613.GB83329@fajrero> (raw)
In-Reply-To: <2007-03-18T23-36-32@devnull.michael-prokop.at>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
I have a modified espeak-generic.conf at
http://tspivey.freeshell.org/espeak-generic.conf. You might want to
modify it again so that it goes through the sox play command, since the
one I have sort of chops - I'm not sure about the latest version of
espeak. I think the blank line deletion still stands - speech dispatcher
sometimes sends just blank lines to espeak, which causes it to pause.
- - Tyler
On Sun, Mar 18, 2007 at 11:45:10PM +0100, Michael Prokop wrote:
> * Hynek Hanke <hanke@brailcom.org> wrote:
> > Michael Prokop p??e v Ne 18. 03. 2007 v 15:59 +0100:
>
> >> "I however find Espeak does not sound quite as clear to me. I like
> >> the current synthesizer that is being used."
> >> What benefit would espeak bring compared to eflite?
>
> > Compared to eFlite, eSpeak is a multi-lingual synthesizer.
> > Although the quality of languages is very variable, it is possible to
> > use it for MANY languages in a way that it is understandable (useful).
> > The span is even wider than documented, because for example for Czech it
> > is possible to use it with the Polish voice and understand it. I believe
> > this is the case for other close languages too. And I'm amazed on how
> > fast voices for new languages are being added, although of only basic
> > quality. eFlite is nowhere near this...
>
> Ok, thanks.
>
> >> Disclaimer: I can't promise anything regarding adding espeak. We are
> >> running out of space so the ISO fits within 700MB on grml always...
>
> > If necessary for disk space reasons, I highly recommend dropping Flite
> > in favor of eSpeak.
>
> Ok. When I'm removing libflite1, besides flite and eflite also
> brltty-flite and speech-dispatcher will disappear. This would bring
> me >15MB of disk space whereas espeak needs only 1200kB at total, so
> definitely appreciated from my side.
>
> But I've to take a look at espeak and its configuration first of
> all. Any help and feedback regarding espeak's configuration on grml
> is highly welcome.
>
> -mika-
> --
> ,'"`. http://www.michael-prokop.at/
> ( grml.org -? Linux Live-CD for texttool-users and sysadmins
> `._,' http://www.grml.org/
>
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (FreeBSD)
iD8DBQFF/cg8TsjaYASMWKQRAhxkAJ91wnuw8mwAgOwvKsQwNuyY7iXsPwCfWpmB
pgaKTf15wBZaRgrGpF9auyc=
=JcHS
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
Nick Gawronski
` Chris Norman
` Nick Gawronski
` Tyler Spivey
` Gregory Nowak
` Nick Gawronski
` Michael Prokop
` Nick Gawronski
` Gregory Nowak
` Tom Moore
` Nick Gawronski
` Gregory Nowak
` Tom Moore
` Nick Gawronski
` Adam Myrow
` Nick Gawronski
` Michael Prokop
` Jonathan Duddington
` Michael Prokop
` Hynek Hanke
` Michael Prokop
` Tyler Spivey [this message]
` Michael Prokop
` Nick Gawronski
` Jonathan Duddington
` Nick Gawronski
` Michael Prokop
` Hynek Hanke
` Michael Prokop
` hanke
` Michael Prokop
` Zachary Kline
` Albert E. Sten-Clanton
` Michael Prokop
` Scott Ford
` Michael Prokop
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=20070318231613.GB83329@fajrero \
--to=tspivey@pcdesk.net \
--cc=speakup@braille.uwo.ca \
/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).