From: "Doug Sutherland" <doug@proficio.ca>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: TTSynth Is Available Again
Date: Tue, 19 Jun 2007 08:16:22 -0500 [thread overview]
Message-ID: <001001c7b274$081cbcc0$ab00a8c0@tenstac> (raw)
In-Reply-To: <35319ac693ebb9e59e798621b87cc9c0@www1.mail.volny.cz>
There has never been source code available for ibm viavoice.
It is not open source, never has been, never will be. What
was provided was a header file to be included in your own
source which allowed you to invoke engine functions. See
the documentation for ibm tts, it's all spelled out.
Hynek Hanke said:
It looks to me that the source code is definitely not available
except for small helper applications like tts_connector which
are useless without the main TTSynth code anyway, am I right? :(
Unless things are different than when I use it, and I don't think
so, there is a binary executable with an API that you can call
from programs. That doesn't make it useless, it just means
the engine is not open source. You shouldn't need to mess
with the engine anyways.
>From what I have seen, I'm pretty sure IBM didn't own the
source for tts, so they can't give it away. It looks to me like
it's a license from eloquence, binary license.
-- Doug
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
hanke
` Luke Yelavich
` Doug Sutherland [this message]
` Janina Sajka
` hanke
-- strict thread matches above, loose matches on Subject: below --
Janina Sajka
` Cody Hurst
` Janina Sajka
` ace
` Gaijin
` Janina Sajka
` Gregory Nowak
` Luke Yelavich
` Doug Sutherland
` Janina Sajka
` Georgina Joyce
` Doug Sutherland
` Jim Grimsby Jr.
` Doug Sutherland
` Georgina Joyce
` Georgina Joyce
` Steve Dawes
` Travis Siegel
` Doug Sutherland
` Travis Siegel
` Doug Sutherland
` Travis Siegel
` Doug Sutherland
` Travis Siegel
` Doug Sutherland
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='001001c7b274$081cbcc0$ab00a8c0@tenstac' \
--to=doug@proficio.ca \
--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).