From: Michael Whapples <mwhapples@aim.com>
To: speakup@braille.uwo.ca
Subject: IBMTTS on slackware
Date: Sun, 01 Jun 2008 20:33:48 +0100 [thread overview]
Message-ID: <1212348828.3140.47.camel@localhost> (raw)
Hello,
I know this has come up before, but I can't remember any actual final
conclusion.
Whilst I thought espeak was fast enough, I found I had to use a windows
machine last week, and it reminded me how I do actually use eloquence in
windows faster than I have espeak. This has got me thinking whether I
should get IBMTTS for linux, but I have a few questions.
I know that IBMTTS requires an old compatibility library, which I am
unsure is provided in slackware. So how could I go about trying to get
this library? Does anyone know of a suitable slackware package for it?
If not how might I go about providing this myself from source (I had a
look around for the source code I might need, but all libstdc++ seems to
have numbers such as 6.0.x etc much highrt than what the TTSynth site
suggests, 2.9.6 or 2.9.5). Could it be possible to use a package from a
different distribution, eg. I remember back in the days when I used
trplayer, I could use rpm2tgz to convert the realplayer 8 package into a
slackware package and it worked fine, but I suspect that for libstdc++
compatibility libraries things may not be so simple.
This brings me on to another question, whether to use voxin or ttsynth?
The ttsynth website says there won't be any support provided, so I guess
this means if I buy ttsynth and can't get it working then I am on my own
and may have wasted money on it. Might things be better with voxin,
their website says that voxin includes the libstdc++ compatibility
library (I guess for debian or ubuntu as those are the distros
mentioned).
Alternatively I am wondering whether it would be best save the money and
stick with espeak as it is good and works, where as ibmtts sounds like I
may hit all sorts of compatibility issues and potentially have no
support from the seller.
Michael Whapples
next reply other threads:[~ UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
Michael Whapples [this message]
` William Hubbs
` Willem van der Walt
` Nick Stockton
` Michael Whapples
` Alex Snow
` Michael Whapples
` Nick Stockton
` Nick Stockton
` Michael Whapples
` Nick Stockton
` Michael Whapples
` Nick Stockton
` Michael Whapples
` Nick Stockton
` Michael Whapples
` Nick Stockton
` Tomas Cerha
` Nick Stockton
` Janina Sajka
` Frank Carmickle
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=1212348828.3140.47.camel@localhost \
--to=mwhapples@aim.com \
--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).