-
-
Notifications
You must be signed in to change notification settings - Fork 784
remove SAPI4 from NVDA #18310
Copy link
Copy link
Labels
api-breaking-changeblocked/needs-internal-fixcomponent/speech-synth-driversp3https://github.com/nvaccess/nvda/blob/master/projectDocs/issues/triage.md#priorityhttps://github.com/nvaccess/nvda/blob/master/projectDocs/issues/triage.md#priorityrelease/blockingthis issue blocks the milestone releasethis issue blocks the milestone releaserelease/blocking-betatriagedHas been triaged, issue is waiting for implementation.Has been triaged, issue is waiting for implementation.
Milestone
Description
Metadata
Metadata
Assignees
Labels
api-breaking-changeblocked/needs-internal-fixcomponent/speech-synth-driversp3https://github.com/nvaccess/nvda/blob/master/projectDocs/issues/triage.md#priorityhttps://github.com/nvaccess/nvda/blob/master/projectDocs/issues/triage.md#priorityrelease/blockingthis issue blocks the milestone releasethis issue blocks the milestone releaserelease/blocking-betatriagedHas been triaged, issue is waiting for implementation.Has been triaged, issue is waiting for implementation.
Type
Fields
Give feedbackNo fields configured for Feature.
Is your feature request related to a problem? Please describe.
There are serious issues with the SAPI 4 WASAPI implementation affecting users.
Users must toggle an advanced setting to disable WASAPI for SAPI 4.
Having to change an advanced setting is not intuitive or recommended for most users.
Describe the solution you'd like
Due to 64bit migration, we are no longer able to maintain SAPI 4 in NVDA core.
NV Access plans to create an add-on to support legacy 32bit software such as SAPI 4.
Describe alternatives you've considered
Integrating the add-on into NVDA, which would double the size of NVDA.
Additional context
Similar: #18309