Normally, an uppercase letter in the middle of what might look like a word to a sighted person, would in fact be pronounced as a new word by a screenreader, so while Blvariable would sound a bit 'messy', blVariable sounds a bit better, and this is actually the same sort of naming convention would use in old, sighted days, so something like a datatable would have been tblData1 even back then. Stay well Jacob Kruger Blind Biker Skype: BlindZA '...fate had broken his body, but not his spirit...' ----- Original Message ----- From: Andreas Stefik To: programmingblind@xxxxxxxxxxxxx ; Sodbeans Sent: Thursday, June 03, 2010 5:40 PM 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 __________ Information from ESET NOD32 Antivirus, version of virus signature database 5169 (20100603) __________ The message was checked by ESET NOD32 Antivirus. http://www.eset.com