From: Willem van der Walt <wvdwalt@csir.co.za>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: speech dispatcher with speakup
Date: Thu, 3 Jun 2010 16:57:24 +0200 (SAST) [thread overview]
Message-ID: <Pine.LNX.4.64.1006031654340.7407@localhost.localdomain> (raw)
In-Reply-To: <4FD251887829402EBED3B3EA54DAF7C9@kristoffpbctxj>
Try spd-say "some words to say"
from the command-line and if it does not speak, look in the logs.
They are usually in /var/log/speech-dispatcher.
Regards, Willem
On Thu, 3 Jun 2010, Kristoffer Gustafsson wrote:
> Hello!
> Yes, dispatcher is working, but it doesn't say anything.
> /kristoffer
> ----- Original Message ----- From: <trev.saunders@gmail.com>
> To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
> Sent: Thursday, June 03, 2010 4:23 PM
> Subject: Re: speech dispatcher with speakup
>
>
> > Hi,
> >
> > that is error is harmless, the daemon should still start. check by running
> > ps -e | grep speech-dispatcher, you should see a speech-dispatcher process
> > running. If it is running you can test that it is infact usable by
> > telneting to port 6560 on localhost. There will we a opentts releease very
> > soon, but currently you have to get opentts with from
> > git://git.opentts.org/opentts.git.
> >
> > HTH
> > Trev
> > _______________________________________________
> > 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
>
>
--
This message is subject to the CSIR's copyright terms and conditions, e-mail legal notice, and implemented Open Document Format (ODF) standard.
The full disclaimer details can be found at http://www.csir.co.za/disclaimer.html.
This message has been scanned for viruses and dangerous content by MailScanner,
and is believed to be clean. MailScanner thanks Transtec Computers for their support.
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
Kristoffer Gustafsson
` Willem van der Walt
` Kenny Hitt
` Willem van der Walt
` Kenny Hitt
` Kristoffer Gustafsson
` Kenny Hitt
` Kristoffer Gustafsson
` trev.saunders
` Kristoffer Gustafsson
` trev.saunders
` Willem van der Walt [this message]
` Kenny Hitt
` Kristoffer Gustafsson
` trev.saunders
` Kristoffer Gustafsson
` trev.saunders
` Kristoffer Gustafsson
` trev.saunders
` Kristoffer Gustafsson
` Kenny Hitt
` Kristoffer Gustafsson
` trev.saunders
` Kristoffer Gustafsson
` Kenny Hitt
` covici
` Kenny Hitt
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=Pine.LNX.4.64.1006031654340.7407@localhost.localdomain \
--to=wvdwalt@csir.co.za \
--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).