From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from cpe-24-221-98-238.az.sprintbbd.net ([24.221.98.238] helo=lnx1.holmesgrown.com ident=root) by speech.braille.uwo.ca with esmtp (Exim 3.32 #1 (Debian)) id 16PeXj-00042m-00 for ; Sun, 13 Jan 2002 01:54:59 -0500 Received: from lnx3.holmesgrown.com (steve@lnx3.holmesgrown.com [192.168.1.5]) by lnx1.holmesgrown.com (8.9.3/8.9.3) with ESMTP id XAA21357 for ; Sat, 12 Jan 2002 23:55:00 -0700 Date: Sat, 12 Jan 2002 23:56:11 -0700 (MST) From: Steve Holmes To: Subject: Re: speakup and programming code In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: speakup-admin@braille.uwo.ca Errors-To: speakup-admin@braille.uwo.ca X-BeenThere: speakup@braille.uwo.ca X-Mailman-Version: 2.0.7 Precedence: bulk Reply-To: speakup@braille.uwo.ca List-Help: List-Post: List-Subscribe: , List-Id: Speakup is a screen review system for Linux. List-Unsubscribe: , List-Archive: Hey, I like that "mixed case" feature as well. This concept of capitalizing the first letter of each implied word in program variables is heavily stressed in coding standards for Visual Basic. I rather like the idea, even as a coding standard for other languages. If a screen reader can logically break these up into words and speak them separately, then it is even that much better. On Sat, 12 Jan 2002, Charles Hallenbeck wrote: > Recent posts by Thomas Ward and others have prompted this > suggestion for a speakup feature that might greatly facilitate > things for people who deal with program code such as C or C++, > and might make exception dictionaries less critical to implement. > > Many times the mixture of capitalization within an alphabetic > string is unusual in program code, and of course it is important. > I first ran across this many years ago with the name of the > popular data base package "d base ii". Now what you should have > heard inside the quotes is what everyone says when they pronounce > it, but "d base" is actually written "dBASE", and I defy you to > hear that correctly without spelling it out character by > character. > > Here is my suggestion: When speakup is sending a series of > letters to the synth and notices that (1) the current char is > upper case, and (2) the last char sent was lower case, then (3) > before sending the current char it should send whatever is needed > to break the current string into two parts. Maybe that would be a > CR, or a space, or some unspoken control char, or whatever. The > result would be "d base" instead of "dBASE", and C programmers > will recognize immediately that there will be zillions of similar > funny case mixtures that will be spoken more correctly if the > transition from lower to upper case within a string is broken up > with a neutral unspoken element that serves only to cause the > synth to pronounce what it has already received and treat the > following as a new word. > > This would perhaps be an inexpensive speakup modification that > would dramatically improve its performance for some of us. > > Chuck > > > *<<<=-=>>>*<<<=-=>>>*<<<=-=>>>*<<<=-=>>>* > Visit me at http://www.mhonline.net/~chuckh > The Moon is Waning Crescent (1% of Full) > > > _______________________________________________ > Speakup mailing list > Speakup@braille.uwo.ca > http://speech.braille.uwo.ca/mailman/listinfo/speakup >