From: Hynek Hanke <hanke@brailcom.org>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: grml spelling issues
Date: Sun, 18 Mar 2007 21:03:03 +0100 [thread overview]
Message-ID: <1174248183.3368.23.camel@chopin> (raw)
In-Reply-To: <2007-03-18T15-54-56@devnull.michael-prokop.at>
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...
> 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.
Have a nice day,
Hynek Hanke
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 [this message]
` Michael Prokop
` Tyler Spivey
` 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=1174248183.3368.23.camel@chopin \
--to=hanke@brailcom.org \
--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).