You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Reported by mdcurran on 2007-12-13 09:55
Currently the voice and variant values in nvda.ini are stored as ints. This is a problem when new voices or variants are added to the speech synth, as the indexing can break. NVDA should store the name of the voice or variant in nvda.ini, so that voice and variant selection will be more accurate. Other than changing config code, it may be an idea to change all synth drivers so that voices are set/read by name, not index. ESpeak can probably handle this quite well, though sapi4 and sapi5 may have some issues. This should only be implemented when its clear that eSpeak, sapi4 and sapi5 can all work with voice names with no problems. Implementing this change will also make nvda.ini more readable to users as they will see the voice name, not just a number.
The text was updated successfully, but these errors were encountered:
Reported by mdcurran on 2007-12-13 09:55
Currently the voice and variant values in nvda.ini are stored as ints. This is a problem when new voices or variants are added to the speech synth, as the indexing can break. NVDA should store the name of the voice or variant in nvda.ini, so that voice and variant selection will be more accurate. Other than changing config code, it may be an idea to change all synth drivers so that voices are set/read by name, not index. ESpeak can probably handle this quite well, though sapi4 and sapi5 may have some issues. This should only be implemented when its clear that eSpeak, sapi4 and sapi5 can all work with voice names with no problems. Implementing this change will also make nvda.ini more readable to users as they will see the voice name, not just a number.
The text was updated successfully, but these errors were encountered: