On Wed, 16 May 2012, Dave Mielke wrote: > [quoted lines by Nicolas Pitre on 2012/05/16 at 22:11 -0400] > > Hi: > > >This introduce another speech option to determine if whitespaces are > >explicitly spoken, or if they remain silent. > > Thanks. > > I renamed "verbose spaces" to "white space". Speaking spaces non-verbosely > still implies that they're spoken - tersely. > > I also changed how the preference was acted on since it was done in a way > which > impacted more than just autospeak.
You also broke it. :-) With my patch, if the setting was set to "no", a space would mute the speech. you apparently dropped that part. > Perhaps speech cursor navigation also needs some kind of space speaking > preference. If so, the two should probably be merged, and the merged > preference > shouldn't be subject to the autospeak setting. Probably, yes. This is not about generating autospeak events, but rather how spaces are called out during such events. > Also, we'd have to think through > very carefully what each of its values should be. Maybe: "Spaces are: silent / spoken". A third option could eventually be a short beep. Nicolas _______________________________________________ This message was sent via the BRLTTY mailing list. To post a message, send an e-mail to: [email protected] For general information, go to: http://mielke.cc/mailman/listinfo/brltty
