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
Provide speech and braille feedback for common Microsoft Word shortcut keys #1353
Comments
Comment 2 by rameshwar.nagar on 2013-02-18 08:16 This is under process...for more correction. Thanks, Rameshwar Nagar |
Attachment winword.py added by rameshwar.nagar on 2013-02-20 10:14 |
Attachment winword.2.py added by mjrevansiddesh on 2013-02-26 06:38 |
Comment 3 by mjrevansiddesh on 2013-02-26 06:40 Changes: |
Comment 4 by mjrevansiddesh on 2013-02-26 06:52 Changes: |
Comment 5 by praveen on 2013-02-26 10:04
Thanks & Regards |
Comment 7 by rameshwar.nagar on 2013-03-13 13:28 Regards & Thanks, |
Comment 8 by rameshwar.nagar on 2013-03-13 13:30 |
Attachment winword.2.patch added by rameshwar.nagar on 2013-03-14 05:42 |
Attachment winword.patch added by rameshwar.nagar on 2013-03-14 05:43 |
Comment 9 by Amarjit on 2013-03-24 17:24 Above patch implements feature to do announcement of Ctrl+. Details are as follows:
|
Comment 10 by Amarjit on 2013-03-24 17:24 |
Comment 13 by jteh on 2013-03-24 23:21 To implement this correctly, you need to find a way to query the state of these toggles in Word, whether by querying the toolbar buttons or something in the document object model. What you've done reflects the formatting of the current review position, which isn't necessarily the same. There is no need to modify anything in the speech module to do this, nor is there any need to duplicate functions from speech in your Word app module. Finally, this doesn't account for the fact that these shortcut keys can apparently be different in different localisations of Word. Btw, please don't close a ticket as fixed until a fix has been committed. |
Comment 15 by Michael Curran <mick@... on 2014-06-10 03:53
Changes:
|
Comment 16 by surfer0627 on 2014-06-10 05:50 |
Comment 17 by surfer0627 on 2014-06-10 05:55 |
Comment 19 by nvdakor on 2014-06-10 09:30 |
Comment 20 by Michael Curran <mick@... on 2014-06-10 10:25
|
Comment 21 by mdcurran (in reply to comment 19) on 2014-06-10 10:28 |
Comment 22 by nvdakor on 2014-06-10 10:33 |
Comment 23 by ateu on 2014-06-10 14:13 Is it possible to add the select/unselect all command? |
Comment 24 by surveyor on 2014-06-11 08:28 |
Comment 25 by Michael Curran <mick@... on 2014-06-11 11:38
|
Comment 26 by Michael Curran <mick@... on 2014-06-14 03:55
|
Comment 27 by Michael Curran <mick@... on 2014-06-27 23:06
Changes:
|
Comment 28 by mdcurran on 2014-06-27 23:07 |
Comment 29 by Sukil on 2014-06-30 20:23 |
Comment 30 by JamaicanUser on 2014-06-30 20:56 |
Comment 31 by jteh (in reply to comment 29) on 2014-06-30 21:46
We're aware of this. Unfortunately, there's no way to detect the effect of the shortcut without binding it to a key. Translators can provide locale specific gesture mappings; e.g. the Spanish translator could unbind control+b and bind reporting of bold to control+n. |
Comment 33 by surveyor on 2014-07-03 10:24 |
Comment 34 by jteh on 2014-07-03 10:55 |
Comment 35 by surveyor (in reply to comment 34) on 2014-07-04 10:43
Yes, the same issue was already valid for other messages for example message heathers such as From, Subject, Date etc. Even if the user is using windows live mail or outlook in English, the heathers are being read in Turkish. Anyway, it's not a big issue. Besides, the binding control+r is used for right alignment in English version, while the same key press is used for centering text in Turkish version of Office. |
Comment 36 by surveyor (in reply to comment 35) on 2014-07-04 11:06 |
Comment 37 by jteh (in reply to comment 36) on 2014-07-05 08:42
Yes, that's correct. |
Comment 38 by ateu on 2014-07-13 15:05 |
Comment 39 by jteh (in reply to comment 23) on 2014-07-14 01:16
If you're talking about control+a (for English), it already announces that the text is selected. |
Comment 40 by blindbhavya on 2014-07-15 10:55 |
Comment 41 by blindbhavya on 2014-07-15 11:03 |
Comment 42 by surveyor on 2014-07-16 11:34 |
Comment 43 by jteh (in reply to comment 42) on 2014-07-17 00:37
There's not really any useful feedback we can provide for these. They don't have a state we can actually report; they just make a change to the text. All we'd be doing is reporting a static message like "paragraph moved" or "case changed", which is not particularly useful, as it doesn't really inform the user of the exact change. |
Comment 44 by blindbhavya on 2014-07-18 13:18 |
Comment 45 by k_kolev1985 on 2014-07-18 13:28 I don't think it is a good idea, unless there is a way to check if the action was really performed or not. Because, the "save" command in MS Word doesn't always use the CTRL+S keystroke. For example, on my Windows 8.1 machine and Office 2013 (both in bulgarian), the keystroke to save is not CTRL+S, but Shift+F12, and I haven't changed - it was set that way by default. BTW: For some actions in MS Office products, you can set MS Office to use sound feedback. Then you need to download an installer for the soundpack for MS Office, install it, set it (if necessary) in Control Panel -> Sound. Then will have sound feedback for some actions in MS Office, including for the save command. Interestingly enough, that was the way that I've discovered that CTRL+S was not performing the "save" command :). |
Comment 46 by ateu (in reply to comment 39) on 2014-11-13 12:42
Strangelly, in my language, Brazilian Portuguese, this information is not provided. Here, the shortcut to select/unselect all is control+t, and when It's pressed, NVDA says nothing. |
Comment 47 by jteh (in reply to comment 46) on 2014-11-19 04:26
You'd need to provide a locale specific gesture binding. See #4478, which discusses this same issue for Spanish. |
Reported by wildcat11 on 2011-02-03 22:14
For example when pressing control plus e nvda doesn't say centered it is silent.
Blocking #2573, #3846, #3862
The text was updated successfully, but these errors were encountered: