I forget which screen reader I saw this in, but it might be a good idea, as an option, anyway, to have the program say "cap" before a single capital letter and "cap cap" before something in all capitals. I've also seen a tone or double tone respectively used in the same way. Pitch works reasonably well, but I sometimes found that the slight annoyance of hearing "cap" or a tone was outweighed a bit by its being a clearer indicator. I don't know if what I suggest is feasible, so mention it only as a user who might find it helpful. Al -----Original Message----- From: speakup-bounces@xxxxxxxxxxxxxx [mailto:speakup-bounces at braille.uwo.ca] On Behalf Of Tony Baechler Sent: Thursday, October 01, 2009 2:06 AM To: Speakup is a screen review system for Linux. Subject: Re: dectalk issues I think I would rather have caps_start hard-coded into the driver. I don't really see why an average user would need to change it. I don't like your two options because they are unconventional and add extra noise. The word "cap" before every capital gets very annoying very quickly. The tone could work, but we have the same problem. How do you determine what value to use for the tone setting? I guess you could set caps_start to sound a tone and a user could change it if they wish, but that means sounding a tone before every capital letter. I like my idea better, just have the driver add 50 or 60 to the current pitch and use that. The relative value could be represented by %d or something, so caps_start could be something like: [:dv ap %d ] On 9/30/2009 10:46 AM, William Hubbs wrote: > So, the way I see it is we have two options: > > 1) drop voice support and force everyone to use paul. > > 2) find another way to do caps indication such as say "cap" or use the > tone generator facility in the dectalks (see the [:tone] command). > _______________________________________________ Speakup mailing list Speakup at braille.uwo.ca http://speech.braille.uwo.ca/mailman/listinfo/speakup
