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

Bug report: All-cap strings spelled with TruVoice #8668

Open
LarrySilvermintz opened this issue Aug 23, 2018 · 5 comments
Open

Bug report: All-cap strings spelled with TruVoice #8668

LarrySilvermintz opened this issue Aug 23, 2018 · 5 comments

Comments

@LarrySilvermintz
Copy link

Can someone please fix this problem speaking acronyms:
Steps to reproduce
Download and Install L&H TruVoice American English from www.bytecool.com/voices.htm
Set this as the active voice in NVDA.
Actual Behavior
When speaking, any string in all-caps is spelled instead of being pronounced as a word.
Expected Behavior
anything that can be pronounced as a word (acronyms) are indeed treated correctly.
Proposed solution:
Either
a) Fix the default behavior so that anything that can be pronounced as a word (acronyms) are indeed treated correctly.
or
b) modify the speech dictionary dialog box with ability to specify regular-expression-style replace with "capturing group"lowercase.

System Configuration
NVDA Installed 2018.2.1
Windows 7 Professional Version 6.1.7601 Service Pack 1 Build 7601

@josephsl
Copy link
Collaborator

josephsl commented Aug 23, 2018 via email

@Brian1Gaff
Copy link

Brian1Gaff commented Aug 23, 2018 via email

@LarrySilvermintz
Copy link
Author

LarrySilvermintz commented Aug 23, 2018 via email

@josephsl
Copy link
Collaborator

josephsl commented Aug 23, 2018 via email

@jscholes
Copy link

If this is an issue with a particular speech engine, it's probably not the responsibility of the NVDA developers to fix it. However, I do agree that the pronunciation dictionary should offer some sort of text-transform mechanism when using capture groups in regular expressions. Perhaps you could file a separate feature request for that, with some examples of how you think it might work?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants