From: "Adam Myrow" <amyrow@midsouth.rr.com>
To: "'Speakup is a screen review system for Linux.'"
<speakup@braille.uwo.ca>
Subject: RE: eSpeak abbreviation question
Date: Thu, 4 May 2006 17:28:57 -0500 [thread overview]
Message-ID: <000f01c66fca$22e8d900$6401a8c0@dell> (raw)
In-Reply-To: <BAY103-DAV182F030D5BA113DBF600E68EB40@phx.gbl>
Well, I have the Dectalk USB, and it does this sort of thing. It's pretty
annoying when it gets abbreviations wrong. I remember that JAWS for DOS
could turn off the Dectalk abbreviations, but JFW can't. The Accent PC also
has abbreviations, but apparently Speakup knows how to turn them off.
Probably the best option is to have a command that can be sent to the
synthesizer to disable abbreviation processing. I also agree that such
processing should be case sensitive.
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
Dawes, Stephen
` Michael Whapples
` Adam Myrow [this message]
` Laura Eaves
` Hart Larry
` Willem van der Walt
` Michael Whapples
-- strict thread matches above, loose matches on Subject: below --
Lorenzo Taylor
` Gregory Nowak
` Steve Holmes
` Janina Sajka
` Lorenzo Taylor
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='000f01c66fca$22e8d900$6401a8c0@dell' \
--to=amyrow@midsouth.rr.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).