From: Luke Yelavich <themuso@opentts.org>
To: speakup@braille.uwo.ca
Subject: Re: espeak
Date: Tue, 21 Sep 2010 13:26:43 +1000 [thread overview]
Message-ID: <20100921032642.GJ2327@strigy> (raw)
In-Reply-To: <20100920212713.GA9089@lnx3.holmesgrown.com>
On Tue, Sep 21, 2010 at 07:27:13AM EST, Steve Holmes wrote:
> Interesting; Johnathan used to lerk around this list some but I
> haven't seen his name on here for some time. I recall he used to be
> pretty responsive when it came to fixes and improvements.
He did reply to me, which I received, but my guess is his message is caught in the moderation queue, due to an attachment, which is why nobody else saw it. He re-released espeak 1.44.05 on sourceforge, with an updated intonations file. I am in the process of fixing up the Ubuntu package and getting it uploaded.
Luke
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
espeak aerospace1028
` espeak Christopher Brannon
` espeak Steve Holmes
` Luke Yelavich [this message]
-- strict thread matches above, loose matches on Subject: below --
espeak mattias
espeak Juan Hernandez
` espeak Jonathan Duddington
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=20100921032642.GJ2327@strigy \
--to=themuso@opentts.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).