Re: Case sensitivity - feedback welcome
- From: "Donald Marang" <donald.marang@xxxxxxxxx>
- To: <programmingblind@xxxxxxxxxxxxx>
- Date: Thu, 3 Jun 2010 12:29:35 -0400
I am not a code professional, I just do it as a hobby. My ears sometimes have
difficulty hearing the pitch change most text to speech engines prefer. What
is prosody? Is it similar to the pitch change method?
In JAWS, I had to create a special Speech and Sounds Scheme that verbally says
"Cap" before individual characters when typing and reviewing by character. It
also says "AllCaps" when word typing echo is enabled and when reviewing by
word. Having it announce Caps when reading line by line, by sentence, or a
SayAll I find not necessary and just annoying. I do not use this all of the
time, but in JAWS, I can switch to this scheme quickly with Insert + Alt + S or
just make it load for certain applications.
I also have the Insert + ` key cycle through All, Most, Some and None
punctuation levels. This is helpful when coding.
Don Marang
From: Andreas Stefik
Sent: Thursday, June 03, 2010 11:40 AM
To: programmingblind@xxxxxxxxxxxxx ; Sodbeans
Subject: Case sensitivity - feedback welcome
Hey folks,
Our development team over here is working on the finishing touches on the
Sodbeans project before release, which is on schedule for early July (Hooray!).
One of the bugs currently listed in our bug database is that our text-to-speech
engine doesn't distinguish between "case" in variable names. As I go through
and use Voice Over (I'm on mac at the moment), I notice that it doesn't
distinguish between case in words either, although, like most screen readers,
it uses prosody to indicate case for specific letters.
So, I have two questions:
1. How do most blind individuals deal with case and case sensitivity while
programming? My guess is that most people, if there's a case issue, have go
through a variable character by character. Is there other strategies? Do other
screen readers have features for dealing with these issues?
2. All else being equal, would it be desirable for the blind community to have
a programming language be completely case insensitive? Or, alternatively,
should we output special auditory cues if something is in Camel Case?
Any thoughts the community is willing to offer would be appreciated. What we
really want to know is, is this issue a really big deal, or does it not cause
many problems in practice?
Stefik
Other related posts:
