From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from [204.233.198.50] (helo=linserver.complex) by speech.braille.uwo.ca with esmtp (Exim 3.32 #1 (Debian)) id 16PQpL-0000dn-00 for ; Sat, 12 Jan 2002 11:16:16 -0500 Received: (from gnowak1@localhost) by linserver.complex (8.11.4/8.10.2) id g0CGFZ800269 for speakup@braille.uwo.ca; Sat, 12 Jan 2002 10:15:35 -0600 Date: Sat, 12 Jan 2002 10:15:35 -0600 From: Gregory Nowak To: speakup@braille.uwo.ca Subject: Re: speakup and programming code Message-ID: <20020112101535.A265@uic.edu> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from chuckh@mhonline.net on Sat, Jan 12, 2002 at 07:25:28AM -0500 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: Grate sugestion, but it wouldn't work for everything. For example, something like "printf" begines with a lowercase p, and ends with a lowercase f, which would mean that it wouldn't get broken up if I understand your implementation of it. Greg On Sat, Jan 12, 2002 at 07:25:28AM -0500, 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