-
-
Notifications
You must be signed in to change notification settings - Fork 783
Send dashes to the synthesizer by default #13830
Copy link
Copy link
Closed
Labels
good first issuegithub features these at https://github.com/nvaccess/nvda/contributegithub features these at https://github.com/nvaccess/nvda/contributep4https://github.com/nvaccess/nvda/blob/master/projectDocs/issues/triage.md#priorityhttps://github.com/nvaccess/nvda/blob/master/projectDocs/issues/triage.md#priorityquick fixtriagedHas been triaged, issue is waiting for implementation.Has been triaged, issue is waiting for implementation.z goodForNewDev (archived)z goodfirstissue (archived)
Milestone
Metadata
Metadata
Assignees
Labels
good first issuegithub features these at https://github.com/nvaccess/nvda/contributegithub features these at https://github.com/nvaccess/nvda/contributep4https://github.com/nvaccess/nvda/blob/master/projectDocs/issues/triage.md#priorityhttps://github.com/nvaccess/nvda/blob/master/projectDocs/issues/triage.md#priorityquick fixtriagedHas been triaged, issue is waiting for implementation.Has been triaged, issue is waiting for implementation.z goodForNewDev (archived)z goodfirstissue (archived)
Type
Fields
Give feedbackNo fields configured for issues without a type.
Steps to reproduce:
Actual behavior:
I hear Jean Luc Picard, and 1950 1960
Expected behavior:
The synthesizer knows what it's doing here, so I want to hear these pronounced correctly.
This should also apply to —. – is set to always by default, so should be fine.
System configuration
NVDA installed/portable/running from source:
Installed
NVDA version:
2022.1
Windows version:
Windows 10 X64 Version 21H1 (OS Build 19043.1766)
Name and version of other software in use when reproducing the issue:
Other information about your system:
Other questions
Does the issue still occur after restarting your computer?
Yes
Have you tried any other versions of NVDA? If so, please report their behaviors.
No
If NVDA add-ons are disabled, is your problem still occurring?
Yes
Does the issue still occur after you run the COM Registration Fixing Tool in NVDA's tools menu?
Yes