Re: Naming Conventions in the NVDA Voice Dialogue
I do agree with Nermin and, while I don’t necessarily consider this to be the most important issue to consider, renaming some of these options might make NVDA’s interface to be a bit more intuitive to newer users. I think that the variant option might be more understandable if it could be called Person or Voice with the Voice list being renamed something like Language? I may do a search for this on the Github page and file it as a feature request if it hasn’t already been done.
Blindness Assistive Technology Specialist
Subscribe to the Tech-VI announcement list to receive emails regarding news and events in the blindness assistive technology field.
From: email@example.com <firstname.lastname@example.org> On Behalf Of Quentin Christensen
Sent: Tuesday, May 3, 2022 11:33 PM
Subject: Re: [nvda] Naming Conventions in the NVDA Voice Dialogue
I'm not familiar with the original decisions as to the naming, however, the exact options do depend on the synthesizer in use.
eSpeak NG uses both options. I currently have:
Voice: English (Great Britain)
OneCore only uses voice, which is currently Microsoft George on mine. Although the language isn't specified, each language includes usually two voices (Male and female) - so I could switch between male and female voices of the one language, or change languages entirely by altering the "voice" here.
Microsoft SPeech API Version 5. Works similar to OneCore, although the list does include mention of the language of each voice, eg: Microsoft David - English (United States)
I haven't double checked other synthesizers just now, but my understanding is that some synthesizers will have options to alter one or the other.