public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: "Thomas D. Ward" <tward1978@earthlink.net>
To: <speakup@braille.uwo.ca>
Subject: Re: OT Re: How to get viavoice working (was Re: where did viavoice go?)
Date: Fri, 9 May 2003 15:35:50 -0400	[thread overview]
Message-ID: <002c01c31662$333abf40$b0849641@tward1978> (raw)
In-Reply-To: <20030509162057.GA5705@potpal>

Interesting. Well, I actually helped set it up for a friend, and we are
still working on the setup. Festival was working fine where viavoice is
still having troubles on the persons system.
I've been out of the loop for a while and I assume the guys from the Gnome
access list must know something I'm not aware of at this time.


----- Original Message -----
From: Kenny Hitt <kennyhitt@knology.net>
To: <speakup@braille.uwo.ca>
Sent: Friday, May 09, 2003 12:20 PM
Subject: OT Re: How to get viavoice working (was Re: where did viavoice go?)


> Hi.  I've been told twice now on the gnome-accessibility list that
> festival is the cause of my Gnopernicus not reading much of the
> information in Gnome.  How
> are you getting around that problem with festival?
>
>           Kenny
>
> On Fri, May 09, 2003 at 11:31:33AM -0400, Thomas D. Ward wrote:
> > In all honesty festival is the better choice here. Viavoice is rapidly
> > getting out dated, and it has problems with certain sound cards which
makes
> > speech real choppy.
> > I suggest using festival or freetts with gnopernicus which I have tested
> > with the latest build of gnopernicus on a Red Hat 9 system.
> >
> > ----- Original Message -----
> > From: John Covici <covici@ccs.covici.com>
> > To: <speakup@braille.uwo.ca>
> > Sent: Friday, May 09, 2003 2:03 AM
> > Subject: How to get viavoice working (was Re: where did viavoice go?)
> >
> >
> > > I have been unable to get viavoice to do anything -- I installed
> > > (using alien) viavoice_tts_rtk_5.tar and viavoice_tts_sdk_5.tar, but
> > > when I went into the programs under the samples directory, the
> > > cmdlinespeak compiled, but complained loudly that it couldn't create
> > > an esi handle and seemed to be looking for esi.ini (on Linux?).
> > > Also, the filespeak program wouldn't even compile -- it was
> > > complaining about some c++ errors.
> > >
> > > Has anyone figured out how to get this to work -- I am interested in
> > > it for possibly emacspeak and also for gnopernicus access.
> > >
> > > --
> > >          John Covici
> > >          covici@ccs.covici.com
> > >
> > > _______________________________________________
> > > Speakup mailing list
> > > Speakup@braille.uwo.ca
> > > http://speech.braille.uwo.ca/mailman/listinfo/speakup
> >
> >
> > _______________________________________________
> > Speakup mailing list
> > Speakup@braille.uwo.ca
> > http://speech.braille.uwo.ca/mailman/listinfo/speakup
> >
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup



  reply	other threads:[~ UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 where did viavoice go? cris
 ` Fwd: " Doug
     [not found]   ` <3.0.5.32.20030426133614.00c80718@pop-server.tampabay.rr.co m>
     ` Doug
 ` Doug
   ` How to get viavoice working (was Re: where did viavoice go?) John Covici
     ` Jacob Schmude
       ` John Covici
     ` Thomas D. Ward
       ` OT " Kenny Hitt
         ` Thomas D. Ward [this message]
       ` Thomas Stivers
         ` Thomas D. Ward
           ` Kenny Hitt
             ` Thomas D. Ward
               ` Kenny Hitt
                 ` Thomas D. Ward
                   ` Kenny Hitt
       ` Mike Keithley
         ` Toby Fisher
 ` where did viavoice go? Patrick Turnage

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='002c01c31662$333abf40$b0849641@tward1978' \
    --to=tward1978@earthlink.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).