public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: nick G <nick6489@optonline.net>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: Flite and different voices
Date: Thu, 13 May 2004 18:25:28 -0400	[thread overview]
Message-ID: <009601c43939$31cb1b50$cc00a8c0@nickysp4> (raw)
In-Reply-To: <20040512224356.GA1169@lnx3.holmesgrown.com>

I have Flite installed, just wondering, is there a Gnome speech driver?
Thanks,
Nick
----- Original Message ----- 
From: "Steve Holmes" <steve@holmesgrown.com>
To: <speakup@braille.uwo.ca>
Sent: Wednesday, May 12, 2004 6:43 PM
Subject: Re: Flite and different voices


> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> On Sun, May 09, 2004 at 11:12:02PM +0200, Hynek Hanke wrote:
> > I'm sorry for this, I should have noticed this earlier. Although you
> > change the library to link in the local Makefile, the cmu_us_kal still
> > gets there in a $(LIBS) variable from the global configure.in. If you
> > change it also in speechd/configure.in to link cmu_us_kal16 instead of
> > cmu_us_kal, do a make distclean and then compile everything from
> > scratch (./build.sh, ./configure, make, make install), you should get
> > the better voice.
> 
> Indeed it is the better voice now, thanks.  Note that I changed a
> variable in configure.in that was not LIBS; I forget the name now but
> it was the first reference to cmu_us_kal.  You don't want to change
> the reg_kal...  I also had to change the LDFLAGS in the
> speechd/modules/Makefile to -lcmu_us_kal16 also.  The LIBS variable in
> this Make file was changed due to the forgoing change in configure.in.
> 
> > Still, this is only an ugly solution. I'll try to somehow make it
> > switch voices at runtime in the future, although Flite is absolutely
> > not designed for such things. As for now, I guess I'll only add a
> > compile-time option to the ./configure script for the 0.4 release
> > which should be available by the end of this month.
> 
> Yes the configure options is a good start.
> 
> - -- 
> HolmesGrown Solutions
> The best solutions for the best price!
> http://ld.net/?holmesgrown
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.2.3 (GNU/Linux)
> 
> iD8DBQFAoqisWSjv55S0LfERAnhnAKCLZxR08FbfgBkfpGKUZDQ3w+62TQCgymuI
> Mvh5R5izQItBShne9ZkzPaI=
> =9Z0T
> -----END PGP SIGNATURE-----
> 
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup


  reply	other threads:[~ UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 speakup and cepstral? (fwd) Cheryl Homiak
 ` Cheryl Homiak
 ` Hynek Hanke
   ` speakup and cepstral? Steve Holmes
     ` Cheryl Homiak
       ` Cheryl Homiak
       ` Cheryl Homiak
         ` Steve Holmes
           ` Cheryl Homiak
             ` speakup and Flite 16 Bit Voices Richard Wells
               ` Steve Holmes
                 ` Richard Wells
             ` speakup and cepstral? Steve Holmes
     ` nick G
       ` Steve Holmes
     ` Flite and different voices (was: Re: speakup and cepstral?) Hynek Hanke
       ` Flite and different voices Steve Holmes
         ` Cheryl Homiak
         ` Steve Holmes
           ` Jacob Schmude
           ` Hynek Hanke
         ` Steve Holmes
           ` Hynek Hanke
             ` Steve Holmes
               ` nick G [this message]
     ` speakup and cepstral? Garrett Klein
       ` Chuck Hallenbeck

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='009601c43939$31cb1b50$cc00a8c0@nickysp4' \
    --to=nick6489@optonline.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).