From: Kenny Hitt <kenny@hittsjunk.net>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: speakupconf and software speech
Date: Fri, 21 Jan 2005 23:20:52 -0600 [thread overview]
Message-ID: <20050122052052.GA14072@blackbox> (raw)
In-Reply-To: <20050121170929.GH25591@tomass.dyndns.org>
Hi. Thanks. The problem seems that the caps_start and caps_stop have
quotes added to the actual string. I loolked at the speakupconf script,
but I can't see how the quotes get added.
Kenny
On Fri, Jan 21, 2005 at 11:09:29AM -0600, Thomas Stivers wrote:
> On Fri, Jan 21, 2005 at 10:59:02 AM -0600, Kenny Hitt wrote:
> > Hi. I recently started using speakupconf and noticed a strange problem
> > with software speech.
> > When I do "speakupconf load" with software speech I here quote spoken
> > during a capital letter.
> > For example: if U press a capital a, I hear speakup say "quote a quote".
> > Has anyone else noticed this problem? If so, what was your solution?
>
> I had this problem at one time and was able to fix it by changing the
> contents of /etc/speakup/softsynth/caps_start and
> /etc/speakup/softsynth/caps_stop. I don't recall what it was set to
> before, but now they are set to \x01+3p and \x01-3p respectively which
> seems to work pretty well.
>
> HTH
>
> --
> "Debugging is twice as hard as writing the code in the first place.
> Therefore, if you write the code as cleverly as possible, you are,
> by definition, not smart enough to debug it." - Brian W. Kernighan
>
> Thomas Stivers e-mail: stivers_t@tomass.dyndns.org
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
Kenny Hitt
` Thomas Stivers
` Kenny Hitt [this message]
` Thomas Stivers
` Sean McMahon
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=20050122052052.GA14072@blackbox \
--to=kenny@hittsjunk.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).