New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Controling menu voice and reading voice #847
Labels
Comments
Comment 1 by jteh on 2010-08-22 19:44 |
Yes. However, I'd want to see a use case for having different voices for reading text and reading menus before even considering this. |
The only use case I remember is having the operating system and apps in
english and using all documents, mails and so on in portuguese.
I know some portuguese banks have systems like that...
Rui
…-----Mensagem Original-----
De: James Teh
Data: 19 de julho de 2017 03:25
Para: nvaccess/nvda
Cc: Subscribed
Assunto: Re: [nvaccess/nvda] Controling menu voice and reading voice (#847)
Yes. However, I'd want to see a use case for having different voices for
reading text and reading menus before even considering this.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.
|
Is this not blocked by speech refactoring? |
@ehollig could you please remove the blocked label now since the corresponding issue and PR are closed/merged? Thanks. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Reported by ManuelRamos on 2010-08-22 05:33
It will be very usefull distinguishing between reading and menu voice and maybe also pontuaction voice. In fact, since there are many synths, ones more helpfull to read what appears on the screen; and others, more accurate, to read books but not much eficient to control NVDA's performance; it would be important that user could configurate each function of voice required: perheaps faster when reading menus, slower and different voice for reading, etc.
Blocked by #650
The text was updated successfully, but these errors were encountered: