Skip to content
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

Jump to bottom

Controling menu voice and reading voice #847

Closed
nvaccessAuto opened this issue Aug 22, 2010 · 8 comments
Closed

Controling menu voice and reading voice #847

nvaccessAuto opened this issue Aug 22, 2010 · 8 comments
Labels
close/duplicate feature

Comments

@nvaccessAuto
Copy link

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
@nvaccessAuto
Copy link
Author

Comment 1 by jteh on 2010-08-22 19:44
Changes:
Milestone changed from 2010.3 to None

@LeonarddeR
Copy link
Collaborator

@jcsteh: is it correct that this at least requires #4877?

@LeonarddeR LeonarddeR added feature and removed bug labels Jul 18, 2017
@jcsteh
Copy link
Contributor

jcsteh commented Jul 19, 2017

Yes. However, I'd want to see a use case for having different voices for reading text and reading menus before even considering this.

@ruifontes
Copy link
Contributor

ruifontes commented Jul 19, 2017 via email

@Adriani90
Copy link
Collaborator

Is this not blocked by speech refactoring?

@ehollig
Copy link
Collaborator

ehollig commented Jul 6, 2018

Yes, this is blocked by #7599 and #4877

@ehollig ehollig added the blocked label Jul 6, 2018
@bhavyashah bhavyashah mentioned this issue Aug 19, 2018
Closed
@CyrilleB79
Copy link
Collaborator

@ehollig could you please remove the blocked label now since the corresponding issue and PR are closed/merged? Thanks.

@seanbudd seanbudd removed the blocked label May 5, 2021
@Adriani90
Copy link
Collaborator

Closing as this is already splitted into more issues, especially in favor of #4086, #6615 and #10363.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
close/duplicate feature
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
8 participants
@LeonarddeR @jcsteh @seanbudd @nvaccessAuto @ruifontes @CyrilleB79 @ehollig @Adriani90