public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: "jim grimsby" <jimgrims@pacbell.net>
To: "'Speakup is a screen review system for Linux.'"
	<speakup@braille.uwo.ca>
Subject: RE: Feature Request
Date: Sat, 2 Apr 2005 13:03:19 -0800	[thread overview]
Message-ID: <000301c537c7$69187fc0$220110ac@jim> (raw)
In-Reply-To: <20050402152536.GT11527@rednote.net>

Agreed 

-----Original Message-----
From: speakup-bounces@braille.uwo.ca
[mailto:speakup-bounces@braille.uwo.ca] On Behalf Of Janina Sajka
Sent: Saturday, April 02, 2005 7:26 AM
To: speakup@braille.uwo.ca
Subject: Feature Request


I'm finding I would appreciate a slightly different behavior from the
"read current word" key in Speakup.

In the instance when current word is a single char, I would like it to
acknowledge upper and lower case differences. In other words, I think 5
should behave exactly as 2 does, when the current-word is actually a
single-char in upper case.

Thoughts?


-- 

Janina Sajka				Phone: +1.202.494.7040
Partner, Capital Accessibility LLC
http://www.CapitalAccessibility.Com

Chair, Accessibility Workgroup		Free Standards Group (FSG)
janina@freestandards.org		http://a11y.org

If Linux can't solve your computing problem, you need a different
problem.


_______________________________________________
Speakup mailing list
Speakup@braille.uwo.ca
http://speech.braille.uwo.ca/mailman/listinfo/speakup




  reply	other threads:[~ UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Janina Sajka
 ` jim grimsby [this message]
 ` Sean McMahon
  -- strict thread matches above, loose matches on Subject: below --
 feature request Doug Smith
 ` Samuel Thibault
   ` Adam Myrow
 Feature Request Janina Sajka
 ` David Csercsics
   ` Janina Sajka
     ` Tyler Spivey
       ` Janina Sajka
       ` Chuck Hallenbeck
 ` Chuck Hallenbeck

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='000301c537c7$69187fc0$220110ac@jim' \
    --to=jimgrims@pacbell.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).