From: Luke Yelavich <themuso@opentts.org>
To: speakup@braille.uwo.ca
Cc: jonsd@talktalk.net
Subject: Re: Minor hiccups with espeak 1.44.05 and espeakup 0.71-3 on Arch
Date: Fri, 17 Sep 2010 11:37:17 +1000 [thread overview]
Message-ID: <20100917013717.GB31340@strigy> (raw)
In-Reply-To: <alpine.LNX.2.00.1009161754580.4007@localhost.localdomain>
On Fri, Sep 17, 2010 at 10:58:11AM EST, Zachary Kline wrote:
> Hi All,
> Just a heads up of sorts. I've noticed occasional complaints from
> Espeak 1.44.05 about getting bad intonation data when used with
> Espeakup 0.71. This is on my ArchLinux system, updated earlier
> today.
> Occasional tonal strangeness seems to be the only issue so far,
> other than some decidedly odd pronounciations in the latest
> versions of Espeak which previously were correct.
Can verify this with espeak 1.44.05 on Ubuntu amverick. Note for ubuntu users on Maverick, I kept the 1.44.04 version number, but updated to the 1.44.05 data.
CCing Jonathan.
Luke
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
Zachary Kline
` Luke Yelavich [this message]
` Christopher Brannon
` Willem van der Walt
` Zachary Kline
` Chuck Hallenbeck
` Steve Holmes
` Zachary Kline
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=20100917013717.GB31340@strigy \
--to=themuso@opentts.org \
--cc=jonsd@talktalk.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).