Mirabella, Mathew J
Mathew.Mirabella at team.telstra.com
Mon Mar 3 17:28:27 EST 2003
hi. i get the command error in parameter thing with the dec express too.
i just read a few more messages on this list, and realised that there may be a cvs version more recent than the one i am using.
i am using the speakup 1.0 that comes with the red hat 8 cds. but with the updated kernal.
it reports speakup as the cvs version of some time mid or late 2002. What is the date of the most recent release to CVS?
From: Gene Collins [mailto:collins at gene3.ait.iastate.edu]
Sent: Tuesday, 4 March 2003 4:10 AM
To: speakup at braille.uwo.ca
Subject: Re: Speakup Bugs
Hi Luke. When you report bugs, you should report bugs against the CVS
version of Speakup, since the bugs found in the standard version may
have already been fix. Speakup says zed because Kirk is Canadian and
that's the way they pronounce it. If you want to change this, you can
edit the values in /proc/speakup/characters. Someone who is using the
Dec Express with the CVS version of Speakup may be able to say, but I
believe the cvs version already fixes the DEC Express command bleed
through problem. Kirk will have to comment on the park/backspace bug,
but I believe this is caused by Speakup only using one set of cursor
position data, which doesn't get changed when the cursor is parked.
In response to your ideas about adding set or configuration file
capabilities to Speakup, make sure you make any changes against the most
recent cvs version. This will save others from reinventing the wheel.
Kirk appreciates all bug reports, and those with the skills to write
Speakup source code and enhance it are always welcome.
>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
>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.
>Speakup mailing list
>Speakup at braille.uwo.ca
Speakup mailing list
Speakup at braille.uwo.ca
More information about the Speakup