-
-
Notifications
You must be signed in to change notification settings - Fork 626
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
eSpeak NG in NVDA 2016.2 does not honor punctuation levels for som punctuation characters #6037
Comments
We're definitely using eSpeak NG now, but the version it reports is incorrect. However, I'm guessing it is an earlier commit than the one which fixes the punctuation problem for Persian. CC @michaelDCurran. Note that @mohammadrezarashad explained elsewhere that the Persian contributor for eSpeak NG has apparently fixed this. So, hopefully we can update safely. |
Latest eSpeak-NG master is now in NVDA next. Is the issue fixed when running a Next snapshot? |
Hello dear friends, ۱۳۹۵-۰۴-۱۷ ۳:۳۷ +۰۴:۳۰ گرینویچ, Michael Curran notifications@github.com:
|
Warning!: |
The upgrade to latest eSpeakNG master has not made its way from NVDA This should happen in a week or so. Thanks Mick On 14/07/2016 4:04 AM, mohammadrezarashad wrote:
Michael Curran |
Thanks so much! ۱۳۹۵-۰۵-۰۴ ۲:۳۳ +۰۴:۳۰ گرینویچ, Michael Curran notifications@github.com:
|
when I press NVDA+F12 for "say time", NVDA announced "colon" between numbers; even if I set the punctuation speeking to "none" for example, 13 colon 29. This problem also exists for closed parenthesis ")". Worst of all, when I set punctuation to all, NVDA reads one ) twice.
This problem occurs when I use eSpeak NG in Persian.
Finally, when I open the LogViewer of NVDA 2016.2, I see in line 14 the following:
Using eSpeak version 1.48.15 16.Apr.15
I have same abovementioned problems with eSpeak 1.48.15 on android, too.
The text was updated successfully, but these errors were encountered: