From: "Doug Sutherland" <doug@proficio.ca>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: TTSynth Is Here At Last
Date: Thu, 7 Jun 2007 19:59:23 -0500 [thread overview]
Message-ID: <000d01c7a968$416ffe20$ab00a8c0@tenstac> (raw)
In-Reply-To: <20070607233948.GI26670@rednote.net>
Hmm wow I loved viavoice for linux while it was still compatible.
I'm wondering how this module was made to work. After the
viavoice was no longer compatible, I managed to do a painful
build where I had two versions of glibc installed, one for use
with viavoice and one that was current. Spent many hours on
this, and although it worked, I eventually gave up on viavoice.
Does this mean capital accessibility is able to rebuild the ibm
viavoice (actually eloquence inside) tts engine for compatibility
with new c libararies? Or does it use some kind of wrapper
code as compatibility layer? Can programs be compiled from
source using the eci.h header?
Glad to see viavoice is still alive.
-- Doug
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
Janina Sajka
` Jan Buchal
` Hart Larry
` Janina Sajka
` C.M. Brannon
` David Poehlman
` Janina Sajka
` David Poehlman
` Janina Sajka
` Brent Harding
` Janina Sajka
` Doug Smith
` David Poehlman
` Brent Harding
` Doug Smith
` Kerry Hoath
` David Poehlman
` David Poehlman
[not found] ` <20070607191102.GC21667@cm.nu>
` Janina Sajka
` Brent Harding
` Janina Sajka
[not found] ` <20070607215604.GA29148@cm.nu>
` Jacob Schmude
` Janina Sajka
` Jacob Schmude
` Janina Sajka
` Doug Sutherland [this message]
` Luke Yelavich
` Luke Yelavich
` Glenn Ervin
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='000d01c7a968$416ffe20$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).