New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cell position and value merged with Excel or other tables and German and french eSpeak #555
Comments
Comment 1 by coffeekingms (in reply to comment description) on 2010-02-11 16:55
I believe that this is a duplicate of #320. jamie, what do you think? I have closed this temporarily as duplicate of 320. please reopen if I'm incorrect. |
Comment 2 by heikofolkerts on 2010-02-11 18:23 |
Comment 3 by jteh on 2010-02-11 22:27 Unfortunately, even using a line feed character causes this problem. The only solution on our side would seem to be to completely separate speech chunks for these items, but this would affect much more than just Excel. It has always been NVDA behaviour not to pause between speaking the name, type, value, etc. of a control. I think we're going to need to work with Jonathan (the eSpeak dev) to try to come up with a solution for this issue, which will probably require changes on both sides. As such, I don't think this is going to be fixed in short order. |
Comment 4 by heikofolkerts on 2010-02-12 20:08 |
Comment 6 by Bernd on 2011-02-26 15:17 |
Comment 7 by Bernd on 2011-04-22 04:53 |
Comment 8 by msuch (in reply to comment 7) on 2011-04-22 05:30 eplying to Bernd:
|
Comment 9 by jteh on 2011-04-22 05:59 |
Comment 10 by Daniel Langeron on 2011-04-25 16:50 I admit it would be very unpleasant to get a reading chopped by numerous between controls and contents. It should also be noted that this inconvenience is not only present in Windows Office applications, but is also present while reading of tables in Web content (e.g. bank statements of personal accounts) I understand that this problem, for the time being, only affects German and French users, but for them it seriously penalizes the use of NVDA ! Daniel |
Comment 11 by Daniel Langeron on 2011-05-01 17:38 I wrote each of the three following rules for each of the two dictionaries. Second Rule Third Rule |
Comment 12 by jteh on 2011-05-03 08:01 |
Comment 13 by Daniel Langeron on 2011-05-03 14:11 For SVOX Pico - French voice: |
Comment 14 by jteh on 2011-05-05 10:21 |
Comment 15 by msuch (in reply to comment 14) on 2011-05-05 11:15
The thousand separator is one space. |
Comment 16 by Daniel Langeron on 2011-05-05 17:38
Thank you for your support. |
Comment 17 by orcauser on 2011-05-05 19:02 Thank you. |
Comment 18 by jteh on 2011-05-05 21:42 @orcauser: Perhaps, but solving #320 is far more subjective and far more difficult. Even if we could do that for Excel, we couldn't really do it for tables elsewhere because the table cell is often an ancestor of the content. Anyway, that should be discussed further in #320. |
Comment 19 by jteh on 2011-05-19 07:05 |
Comment 20 by del65 on 2011-12-17 22:27 |
Comment 21 by jteh on 2011-12-28 21:45 |
Reported by heikofolkerts on 2010-02-11 16:31
When using NVDA in Excel 2003 using the german default settings, the cell position and values are pulled together, so that it sounds wrong.
Example:
a1 = 300
a2 = 500
will be read like
a 1300
a 2500
It irritated me so much, that I first thought my formula was wrong.
The speach has to tread the cell position and the value separately.
This defect makes excel allmost unusable without a braille display.
The text was updated successfully, but these errors were encountered: