public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: "Tyler Littlefield" <tyler@tysdomain.com>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: a quick question
Date: Fri, 20 Jun 2008 12:22:34 -0600	[thread overview]
Message-ID: <000901c8d302$9caf5230$0201a8c0@tdsportable> (raw)
In-Reply-To: <20080620175837.GA13491@localhost.localdomain>

Yeah, I'm still using debian. and thanks. I wasn't aware that that file 
existed. I'm trying to read more docs before I ask. I did probe around the 
manpages some, but didn't see what I needed.
Thanks again,
Thanks,
~~TheCreator~~
Visit TDS for quality software and website production
http://tysdomain.com
visit the piratecafe for programming related resources:
http://piratecafe.net
msn: tyler@tysdomain.com
skype: st8amnd127
----- Original Message ----- 
From: "Gregory Nowak" <greg@romuald.net.eu.org>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Sent: Friday, June 20, 2008 11:58 AM
Subject: Re: a quick question


> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> In that case, try increasing the loglevel for speech-dispatcher. Also,
> assuming you're still using debian, you need to allow localhost to
> access festival, it isn't allowed out of the box. Instructions on
> doing this are in /usr/share/docs/festival/README.Debian. Also, if
> your final intent is to move to espeak, getting festival working
> first, and then moving to espeak makes no sense, and is just a waste
> of your time/effort. If going to espeak is your final intent, skip
> festival altogether, and go to espeak directly.
>
> Greg
>
>
> On Fri, Jun 20, 2008 at 10:52:05AM -0600, Tyler Littlefield wrote:
>> Hello,
>> I'll switch to espeak after I've gotten it working--flite/festival are
>> the supported ones right now in the config.
>> The speech-dispatcher log is empty as are the festival and flite logs.
>> Thanks,
>> ~~TheCreator~~
>> Visit TDS for quality software and website production
>> http://tysdomain.com
>> visit the piratecafe for programming related resources:
>> http://piratecafe.net
>> msn: tyler@tysdomain.com
>> skype: st8amnd127
>
>
> - -- 
> web site: http://www.romuald.net.eu.org
> gpg public key: http://www.romuald.net.eu.org/pubkey.asc
> skype: gregn1
> (authorization required, add me to your contacts list first)
>
> - --
> Free domains: http://www.eu.org/ or mail dns-manager@EU.org
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.6 (GNU/Linux)
>
> iD8DBQFIW+/N7s9z/XlyUyARAkPQAJ9siGa+U5W7G2kRiRULZNCjVhHkpQCg2ZqD
> PO1IRdtkned4WXJcrNpdZIk=
> =QzpH
> -----END PGP SIGNATURE-----
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>
> __________ NOD32 3203 (20080620) Information __________
>
> This message was checked by NOD32 antivirus system.
> http://www.eset.com
>
> 


  reply	other threads:[~ UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Tyler Littlefield
 ` Alastair Irving
   ` Tyler Littlefield
     ` Gregory Nowak
       ` Tyler Littlefield [this message]
       ` Tyler Littlefield
         ` Gregory Nowak
 ` Nick Stockton
   ` Tyler Littlefield
     ` Nick Stockton
       ` Tyler Littlefield
 ` Weird Characters (was: a quick question) luke

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='000901c8d302$9caf5230$0201a8c0@tdsportable' \
    --to=tyler@tysdomain.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).