From: Igor Gueths <igueths@attbi.com>
To: speakup@braille.uwo.ca
Subject: Re: Speakout Users
Date: Wed, 30 Apr 2003 17:26:55 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.44.0304301726030.27631-100000@igueths> (raw)
In-Reply-To: <20030430203725.GB313@lnx3.holmesgrown.com>
Speaking of bugs, is the problem re-initializing the dectalk driver fixed?
I.e., are the punctuation delays properly reset after the driver wakes up
along with Speakup?
May you code in the power of the source,
may the kernel, libraries, and utilities be with you,
throughout all distributions until the end of the epoch.
On Wed, 30 Apr 2003, Steve Holmes wrote:
> I have a question concerning the recent CVS version of Speakup and use
> of the Speakout synth. I only know of John to be another user of it
> but I am wondering if anyone else has had trouble with the tone
> parameter? I found one issue in the speakup_spkout.c module where the
> tone range is defined. John, what is the letter equivelant you try to
> use with speakout? I've usually used 'J'. From what I see so far, the
> base value appears to be off by four positions. It should be 65 and
> not 61. Though that doesn't explain why digits above 4 didn't work
> for me yesterday. I will mess with this some more when I get home
> tonight Since I'm still suffering on a windows box here at work
> talking over an SSH line to mutt.
> --
> Please avoid sending me Word or PowerPoint attachments.
> See http://www.fsf.org/philosophy/no-word-attachments.html
>
> _______________________________________________
> 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: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
Steve Holmes
` Igor Gueths [this message]
` Lorenzo Prince
` Igor Gueths
` Steve Holmes
` Steve Holmes
` Charles Crawford
` 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=Pine.LNX.4.44.0304301726030.27631-100000@igueths \
--to=igueths@attbi.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).