nvaccess / nvda

NVDA, the free and open source Screen Reader for Microsoft Windows
Other
2.08k stars 626 forks source link

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

Open LarrySilvermintz opened 6 years ago

LarrySilvermintz commented 6 years ago

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 commented 6 years ago

Hi, I’m thinking this might be the synthesizer giving you odd results. If this happens with other synthesizers such as Espeak and OneCore, then this is something that we can fix from NVDA side. Thanks.

From: LarrySilvermintz notifications@github.com Sent: Thursday, August 23, 2018 11:14 AM To: nvaccess/nvda nvda@noreply.github.com Cc: Subscribed subscribed@noreply.github.com Subject: [nvaccess/nvda] Bug report: All-cap strings spelled with TruVoice (#8668)

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 http://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

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/nvaccess/nvda/issues/8668 , or mute the thread https://github.com/notifications/unsubscribe-auth/AHgLkDqrBL4hY-YAdBWMb429RZLKE1f2ks5uTvDfgaJpZM4WKCBK .

Brian1Gaff commented 6 years ago

Is this synth the old one we had both sapi4 and 5 versions of some years back? If so it was always somewhat odd in its handling of abbreviations.

I do not have those any more, sorry.

bglists@blueyonder.co.uk Sent via blueyonder. Please address personal E-mail to:- briang1@blueyonder.co.uk, putting 'Brian Gaff' in the display name field.

LarrySilvermintz commented 6 years ago

Hello NVDA gurus, Thank you so much for your instant response. Please let me know if you can possibly help:

You are correct, other voices are handled correctly in NVDA.

Yes, it is the classic SAPI4 speech package, again, the URL for free download is

Download TruVoice: www.bytecool.com/voices.htm

I have been using this voice for many years and am very accustomed to its pronounciation style. It does not have the problem with all-caps words when used by other applications.

So, to repeat, Could you please possibly add the ability in the speech dictionary replace with entry to allow a "convert to lowercase of "capturing group"?

This would also be useful in situations where someone may want to heare a group of words starting with a capital as regular words, whereas the other words that begin with a capital will continue to be identified according to the beep or pitch-change configuration.

Of course, whichever way the problem gets solved is fine with me; the speech-dictionary just seems to be worth suggesting.

Thank you!

Larry Silvermintz


From: Brian Gaff [mailto:notifications@github.com] Sent: Thursday, August 23, 2018 3:51 PM To: nvaccess/nvda Cc: LarrySilvermintz; Author Subject: Re: [nvaccess/nvda] Bug report: All-cap strings spelled with TruVoice (#8668)

Is this synth the old one we had both sapi4 and 5 versions of some years back? If so it was always somewhat odd in its handling of abbreviations.

I do not have those any more, sorry.

bglists@blueyonder.co.uk Sent via blueyonder. Please address personal E-mail to:- briang1@blueyonder.co.uk, putting 'Brian Gaff' in the display name field.

- You are receiving this because you authored the thread. Reply to this email directly, view https://github.com/nvaccess/nvda/issues/8668#issuecomment-415549281 it on GitHub, or mute https://github.com/notifications/unsubscribe-auth/AXygUzeCJfNbgd6fscmCbAVuw n0Orbuyks5uTweIgaJpZM4WKCBK the thread. https://github.com/notifications/beacon/AXygU5evdlynbl5qOudwSIP3Em8n10MDks5 uTweIgaJpZM4WKCBK.gif

josephsl commented 6 years ago

Hi, I see, and thanks for the update. I vaguely remember someone raising a similar issue (or the same thing) in the past. Thanks.

From: LarrySilvermintz notifications@github.com Sent: Thursday, August 23, 2018 4:56 PM To: nvaccess/nvda nvda@noreply.github.com Cc: Joseph Lee joseph.lee22590@gmail.com; Comment comment@noreply.github.com Subject: Re: [nvaccess/nvda] Bug report: All-cap strings spelled with TruVoice (#8668)

Hello NVDA gurus, Thank you so much for your instant response. Please let me know if you can possibly help:

You are correct, other voices are handled correctly in NVDA.

Yes, it is the classic SAPI4 speech package, again, the URL for free download is

Download TruVoice: www.bytecool.com/voices.htm

I have been using this voice for many years and am very accustomed to its pronounciation style. It does not have the problem with all-caps words when used by other applications.

So, to repeat, Could you please possibly add the ability in the speech dictionary replace with entry to allow a "convert to lowercase of "capturing group"?

This would also be useful in situations where someone may want to heare a group of words starting with a capital as regular words, whereas the other words that begin with a capital will continue to be identified according to the beep or pitch-change configuration.

Of course, whichever way the problem gets solved is fine with me; the speech-dictionary just seems to be worth suggesting.

Thank you!

Larry Silvermintz


From: Brian Gaff [mailto:notifications@github.com] Sent: Thursday, August 23, 2018 3:51 PM To: nvaccess/nvda Cc: LarrySilvermintz; Author Subject: Re: [nvaccess/nvda] Bug report: All-cap strings spelled with TruVoice (#8668)

Is this synth the old one we had both sapi4 and 5 versions of some years back? If so it was always somewhat odd in its handling of abbreviations.

I do not have those any more, sorry.

bglists@blueyonder.co.uk Sent via blueyonder. Please address personal E-mail to:- briang1@blueyonder.co.uk, putting 'Brian Gaff' in the display name field.

- You are receiving this because you authored the thread. Reply to this email directly, view https://github.com/nvaccess/nvda/issues/8668#issuecomment-415549281 it on GitHub, or mute https://github.com/notifications/unsubscribe-auth/AXygUzeCJfNbgd6fscmCbAVuw n0Orbuyks5uTweIgaJpZM4WKCBK the thread. https://github.com/notifications/beacon/AXygU5evdlynbl5qOudwSIP3Em8n10MDks5 uTweIgaJpZM4WKCBK.gif

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/nvaccess/nvda/issues/8668#issuecomment-415608923 , or mute the thread https://github.com/notifications/unsubscribe-auth/AHgLkJs95ISK39bgBz0oRsM14QaSWI0jks5uT0D7gaJpZM4WKCBK .

jscholes commented 6 years ago

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?