Closed elliott94 closed 4 years ago
@elliott94:
Apologies - I forgot to mention this.
This is with eSpeak and my Symbol Level set to "Some". No changes have been made to my symbols file.
Thanks.
Okay, I can reproduce this with eSpeak NG, which is built in NVDA 2018.1. It has to do with the space after the bracket. If there is a space after a bracket, the bracket isn't spoken by eSpeak NG, but by other synthesizers. A deeper test for all kind of brackets ()[]{}<>«»
is pending. That should be done during fixing this issue. Maybe the whole thing can be easily fixed by deleting the last character (only if it's U+0020 or U+00A0) in the line, which is sent to the TTS during word navigation.
Therefore the issue title should be now updated too. Thanks.
Fixed by #11167. Testing with NVDA Version: alpha-20400,675c4c54. Closing as works for me.
Tested with NVDA snapshot alpha-17509,0f7c1419 on both Windows 7 and 10 X64.
STR:
This is a (test) with NVDA
You'll notice that NVDA reads the presence of the left bracket, but doesn't make any announcement that the right bracket exists when navigating over it.