Date
1 - 9 of 9
A question regarding Punctuation/symbol pronunciation
|
William
Dear all,
NVDA 2022.4.1 Opening Punctuation/symbol pronunciation dialogue, There is an option as ''' Using the Level field, you can adjust the lowest symbol level at which this symbol should be spoken. ''' And among those options, there is one called 'character' I don't quite understand what does this option mean. Could any one advice me on the effect of this option? Thanks. |
|
|
|
Gene
That's an interesting question.
toggle quoted message
Show quoted text
I entered the dialog and opened the equivalent of context sensitive help by pressing f1 while in the dialog. The user guide opened to the punctuation section. I read the whole section and found no explanation of what the character setting does. Gene On 3/22/2023 8:21 PM, William wrote:
Dear all, |
|
|
|
On Wed, Mar 22, 2023 at 10:47 PM, Gene wrote:
I read the whole section and found no explanation of what the character setting does.- As did I, and found the same thing. The documentation needs to be updated. -- Brian - Virginia, USA - Windows 11 Pro, 64-Bit, Version 22H2, Build 22621; Office 2016, Version 16.0.15726.20188, 32-bit It is much easier to be critical than to be correct. ~ Benjamin Disraeli, 1804-1881 |
|
|
|
Cyrille
Hello
The level "character" allows the symbol not to be spoken, regardless of your punctuation level, except if you navigate by character or spell it. usually, it is used for characters such as "carriage return". I have made a proposal to NVAccess (see #14737) to update the documentation adding the following sentence: "If you set the level on "character", the symbol will not be spoken regardless of the symbol level you are using, except when you navigate by character or when the character is spelt." Feel free to comment there if you feel this phrasing unclear and find a better one. Cheers, Cyrille |
|
|
|
Cyrille,
What do you mean by "when the character is spelt"? The way I read that is, for example, if someone wrote out "carriage return" the phrase would be read, but perhaps I'm missing something. If that's the case, I think that final bit is redundant and reduces clarity rather than enhancing it. I'd expect that if I spell "left parenthesis," for example, that even if I had set the left parenthesis at the character level that those two words would be read because they are two words, not the character. But I want to be certain that I'm not misunderstanding something here. -- Brian - Virginia, USA - Windows 11 Pro, 64-Bit, Version 22H2, Build 22621; Office 2016, Version 16.0.15726.20188, 32-bit It is much easier to be critical than to be correct. ~ Benjamin Disraeli, 1804-1881 |
|
|
|
Cyrille
Hello Brian
toggle quoted message
Show quoted text
Thanks for the feedback. No, I meant when some text is spelt by NVDA (e.g. when pressing two times NVDA+UpArrow or Numpad5 or Numpad8). I have rephrased as follows, only the second sentence is added by me, the first is already today in the User Guide: "- Using the Level field, you can adjust the lowest symbol level at which this symbol should be spoken. If you set the level on "character", the symbol will not be spoken regardless of the symbol level you are using, except when you navigate by character or when some text is spelt." Could you please comment on GitHub if you have some more feedback or ideas? So that NVAccess be in the loop and knows the opinion of everyone expressing his opinion on this change. Thanks. Cyrille On Thu, Mar 23, 2023 at 05:38 PM, Brian Vogel wrote: Cyrille, |
|
|
|
Quentin Christensen
Just a quick note that in order to not lose this, it would be worth filing an issue on GitHub - yes you can file an issue for User Guide fixes :) I'm still trying to catch up on correspondence and everything from CSUN :) On Thu, Mar 23, 2023 at 1:47 PM Gene <gsasner@...> wrote:
--
Quentin Christensen Training and Support Manager Training: https://www.nvaccess.org/shop/ Certification: https://certification.nvaccess.org/ User group: https://nvda.groups.io/g/nvda Facebook: http://www.facebook.com/NVAccess Twitter: @NVAccess |
|
|
|
On Fri, Mar 24, 2023 at 01:41 AM, Quentin Christensen wrote:
it would be worth filing an issue on GitHub - yes you can file an issue for User Guide fixes- Quentin, you are shaking off jet lag!! ;-) Earlier, from Cyrille: I have made a proposal to NVAccess (see #14737) to update the documentation -- Brian - Virginia, USA - Windows 11 Pro, 64-Bit, Version 22H2, Build 22621; Office 2016, Version 16.0.15726.20188, 32-bit It is much easier to be critical than to be correct. ~ Benjamin Disraeli, 1804-1881 |
|
|
|
Quentin Christensen
Oops, yes I blame jet lag :) At least everyone now definitely knows you can file issues for user guide fixes / changes? And re this specific one, it's been merged and heading for NVDA 2023.2. On Sat, Mar 25, 2023 at 2:41 AM Brian Vogel <britechguy@...> wrote: On Fri, Mar 24, 2023 at 01:41 AM, Quentin Christensen wrote: --
Quentin Christensen Training and Support Manager Training: https://www.nvaccess.org/shop/ Certification: https://certification.nvaccess.org/ User group: https://nvda.groups.io/g/nvda Facebook: http://www.facebook.com/NVAccess Twitter: @NVAccess |
|
|