GNOME Bugzilla – Bug 120737
logical function keys lable as given in the tool tip
Last modified: 2004-12-22 21:47:04 UTC
Logical function keys lable should as given in the tool tip. It is as follows " Or" --------> "OR" "And" -----> " AND" "Not" ----> " NOT" " Xor" ----> " XOR" "Xnor" ----> "XNOR"
Could you test with the latest version of gcalctool please. A lot of work has been done recently w.r.t. improving accessibility support and better keyboard handling. The latest version of gcalctool can be found under: http://ftp.gnome.org/pub/GNOME/sources/gcalctool/4.3/ Does the problem still occur with this version (with tooltips on)?
I will use caltool version 4.3, Thanks for the information.
I just tried this with gcalctool v4.3.7 and gnopernicus (with the FreeTTS speech driver). For the five trigonometric buttons, the following is spoken: "logical or" "logical and" "logical not" "logical xor" "logical xnor" Closing as fixed. I should add that FreeTTS makes a right dogs breakfast out of "trigonometric" but that's another story.
With tool tip disabled, all logical functions are working fine accept logical OR. The screen reader reads "logical OR" as "logical ORGAN". With tool tip enabled, logical functions, trignometric functions, arithmetic functions etc. events are sent twice to the screen reader. Hence screen reader reads twice above mentioned functions except numeric keys. gcalctool version used in this is 4.3.9
I'm reopening to fix the "logical organ" problem. My thought on how to fix this would be to substitute a word that sounds like "or" ("oar" for example), and add a comment to the code to say what's going on. This sounds like a localisation problem fraught with disaster though, so can anybody on the gnome-access-bugs alias suggest a better approach? For the second problem, this sounds like something that is more general that for just gcalctool. Does this scenerio happen for other applications? My own feeling is that the accessibility infrastructure is actually doing the right thing. Comments?
I checked with the authors of FreeTTS and got the following response: The token to words module will convert "OR" from "or" to "Oregon" if both of the following two conditions are satisfied: 1. the previous word starts with a capital letter, has a length greater than 2, and is an alphabetical sequence. AND 2. the next word starts with a lowercase, or is null or the start of a new sentence, or if the next word is a zip code. In the case of "Logical OR", both conditions are satisfied. Therefore, it is read as "Logical Oregon". -- So there is a simple fix for this. I just need to change the accessible text to "logical or".
Changes checked into CVS HEAD. Fixed in gcalctool v4.3.14.
The above bug has been verified in gcaltool bersion 4.3.51, cvs build 2.t6. The bug has been verified, XOR & XNOR pronounciation can be set in speech engine dictionary. Hence, this can be closed.