-
-
Notifications
You must be signed in to change notification settings - Fork 626
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
Make Punctuation/symbols dialog use voice language if appropriate #4930
Comments
Comment 1 by leonarddr on 2015-02-18 08:25 |
Comment 2 by leonarddr on 2015-02-18 08:49 |
Comment 3 by leonarddr on 2015-02-18 09:28 |
Comment 4 by jteh on 2015-02-18 10:38 |
Comment 5 by leonarddr (in reply to comment 4) on 2015-02-18 14:53
Ah, got that one.
|
Comment 6 by jteh on 2015-02-19 01:06 |
Comment 7 by Leonard de Ruijter <alderuijter@... on 2015-02-20 04:07
|
Comment 8 by Leonard de Ruijter <alderuijter@... on 2015-02-20 04:07
|
Comment 9 by James Teh <jamie@... on 2015-02-20 04:07
Changes:
|
Comment 10 by jteh on 2015-02-20 04:09 |
Comment 11 by leonarddr on 2015-02-20 11:43
|
Comment 12 by James Teh <jamie@... on 2015-04-08 05:16
Changes:
|
…g en editing symbols, re #4930
…anguage of the symbols currently being edited. * This includes moving the initialisation of the SymbolProcessor to a new initialisation method on SpeechSymbolsDialog * Also, the translatable string for the title is changed to allow inclusion of the language name Re #4930
…" option is enabled, the Punctuation/Symbol pronunciation dialog now correctly uses the voice language. Also, the language for which pronunciation is being edited is shown in the dialog's title. Fixes #4930.
Reported by jteh on 2015-02-18 03:55
(Spun off ticket:4210#comment:18.)
If "Trust voice's language when processing characters and symbols" is enabled, the voice language should be used for the symbol Pronunciation dialog, not NVDA's interface language. This should be relatively trivial: simply use speech.getCurrentLanguage instead of languageHandler.getLanguage. However, we need to test for any unexpected problems.
The text was updated successfully, but these errors were encountered: