On Sat, 1 Mar 2003, Scott Howell wrote: > Not all of these are bugs and probably none of them are. I can't say > much on some of these issues because I don't have a Decktalk, but the > deal on the char Z being spoken as zed is not a bug at all. I'm not It's not? Why doesn't it just say "z", as it does with all of the other characters? If I wanted to hear a phonetic, I would press the key combination therefore. If I am just typing a word, I don't really want to hear any phonetic characters. Further, if it's going to say the Z phonetic when ever it is encountered, why not the B, V, etc.? Also, if this is a feature, where is it documented? > them either. THe point is you are perhaps chasing ghosts on some of > these issues. Perhaps. However, if I hit spell on an acronym "WPHT" (a radio station), for example, I don't really care to hear: "W P H command error in command T", or with "README", I don't want to hear "R E A command error in command D Command Error In String Value 00000000 E". That is annoying, and sounds rather bugish to me. Maybe it is a ghost, but it is still something that seems less like a feature, and more like a bug, to me. > I can say one thing, Speakup is by far a more stable program than > anything that is being used in the windows world and is a hell of a lot > more simple to use. Relacs, I'm not attacking it, just reporting some potential bugs. I'm no fan of Bill's wonderful operating systems, as most know. Luke > On Sat, Mar 01, 2003 at 01:07:36AM -0600, Luke Davis wrote: > > Here are some further potential bugs. > > > > 1. If you backspace [at the shell prompt], while parked, it will not > > speak the deleted characters, but will instead speak [maybe], the > > character on which the reading cursor is located (after). > > > > 2. It says "zepthd", or something such as that, when you read or press a > > "z". > > > > 3. While using the dec express, and having Speakup spell a word in all > > caps, or some caps and some other types, it will read the first two or so > > letters, say "command error in string value", one or more characters > > further, and later, depending on whether the word/acronym/etc., is short > > or long, "command error in parameter", followed by maybe some numbers or > > the like. I think this is the dec's bug, but speakup's problem, in the way > > it is sending data to the DEC. > > > > 4. In the todo file, it suggests that a good new feature, would be to > > check parck status and store it, before doing a console switch. This > > appears to work now. > > > > Luke > > > > > > _______________________________________________ > > Speakup mailing list > > Speakup at braille.uwo.ca > > http://speech.braille.uwo.ca/mailman/listinfo/speakup > > _______________________________________________ > Speakup mailing list > Speakup at braille.uwo.ca > http://speech.braille.uwo.ca/mailman/listinfo/speakup >
