public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: Hynek Hanke <hanke@brailcom.org>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: Espeak Problems
Date: Tue, 27 Feb 2007 21:41:26 +0100	[thread overview]
Message-ID: <1172608887.7608.19.camel@chopin> (raw)
In-Reply-To: <BAY102-DAV1970406A845E0A2F9C1BD8F820@phx.gbl>

On Tue, 2007-02-27 at 12:05 -0800, Zachary Kline wrote:
> I did not do this, actually.  When I did, the thing works now.
> What I'm wondering is how to change punctuation settings?  I'm not getting 
> any punctuation at all spoken, and I want to get at least some.  (Changing 
> defaultpunclevel in speechd.conf didn't seem to do the trick, unless I need 
> to reboot the machine first?)

Hi,

this is a problem that is being worked on. If you need just to make it
work for Speakup in English, the trick for now is to run speechd-up
with the -t (or --dont-init-tables option). Speakup will care of
punctuation, but this only works for English.

If you want internationalization, don't do this. Modify
the /etc/speech-dispatcher/modules/espeak-generic.conf (or similar path)
so that the option GenericExecuteSynth contains the --punct parameter
for eSpeak

This should work:

GenericExecuteSynth \
"echo \"$DATA\" | espeak -w /tmp/espeak.wav --punct -v $VOICE -s $RATE
-a $VOLUME -p $PITCH --stdin && aplay /tmp/espeak.wav"

Make sure GenericStripPunctChars is commented out with the # sign. (It
is by default.)

This second way works with internationalization and will likely result
in better synthesis etc. However, you will not be able to switch between
punctuation on and of at runtime.

Sorry for the hacks. We are working on it.

Have a nice day,
Hynek Hanke




  reply	other threads:[~ UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Zachary Kline
 ` Hynek Hanke
   ` Zachary Kline
     ` Hynek Hanke [this message]
       ` Steve Holmes
         ` Hynek Hanke
           ` Steve Holmes

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=1172608887.7608.19.camel@chopin \
    --to=hanke@brailcom.org \
    --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).