You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Reported by daTscharlie on 2008-11-24 21:30
Hello James, different languages and web sites using different quotes - sometimes NVDA speaks the last word between quotes as single characters.
The text was updated successfully, but these errors were encountered:
Comment 1 by jteh on 2008-11-25 01:07
I assume you mean it spells the word? This is an issue with the speech synth being used. Some synths will spell a word if they detect an unknown character. Please confirm if this is correct. In this case, there is little that can be done on the NVDA side; we should not arbitrarily ignore characters because a synth cannot handle them. However, you can create a speech dictionary to work around this.
Comment 2 by daTscharlie (in reply to comment 1) on 2008-11-25 02:04
Replying to jteh:
I assume you mean it spells the word? This is an issue with the speech synth being used. Some synths will spell a word if they detect an unknown character. Please confirm if this is correct. In this case, there is little that can be done on the NVDA side; we should not arbitrarily ignore characters because a synth cannot handle them. However, you can create a speech dictionary to work around this.
I'm using IBM ViaVoice SAPI4 version 6.4.1.0 and your work around has solved this issue. Thank you very much.
Comment 3 by jteh on 2008-11-25 18:08
Out of interest, does this problem occur for you with the in-built eSpeak synthesiser?
Changes:
Changed title from "NVDA speaks last word between quotes in Firefox sometimes characterwise" to "NVDA sometimes spells last word between quotes in Firefox"
Added labels: wontfix
State: closed
Reported by daTscharlie on 2008-11-24 21:30
Hello James, different languages and web sites using different quotes - sometimes NVDA speaks the last word between quotes as single characters.
The text was updated successfully, but these errors were encountered: