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

The word rename is spoken incorrectly #1991

Closed
nvaccessAuto opened this issue Dec 9, 2011 · 5 comments
Closed

The word rename is spoken incorrectly #1991

nvaccessAuto opened this issue Dec 9, 2011 · 5 comments

Comments

@nvaccessAuto
Copy link

Reported by briang1 on 2011-12-09 05:52
As you can hear the word re-name is said as ername. This shows up in context menus a lot of course.
At this time I do not know if this is espeak or nvda. However its only just started ocurring and I did notice a change in espeak version.
The snap I'm using is 4837.

@nvaccessAuto
Copy link
Author

Comment 1 by jteh on 2011-12-09 06:37
eSpeak just got updated to 1.46.01. This is a bug in eSpeak.
Changes:
Milestone changed from None to 2012.1

@nvaccessAuto
Copy link
Author

Comment 2 by briang1 on 2011-12-09 06:47
I suspected it was. The temp fix here is to use the voice dictionary and add re-name as the substitute for the word. However it will probably crop up in other words. Can you file a bug report?

@nvaccessAuto
Copy link
Author

Comment 3 by jonsd on 2011-12-09 15:06
Fixed now in eSpeak development version 1.46.09, available at:
http://espeak.sourceforge.net/test/latest.html

If you wish, you can update just the data file: espeak-data/en_dict to fix this problem.
The corresponding data source files are dictsource/en_list, dictsource/en_rules.

@nvaccessAuto
Copy link
Author

Comment 4 by ateu on 2012-01-08 10:05
Hi,

New stabe version has been released, 1.46.2.

Ef this problem was not fixed by other way, it's the solution.

Thanks

@nvaccessAuto
Copy link
Author

Comment 5 by jteh on 2012-01-11 04:46
3370715 requires eSpeak 1.46.02. I've updated our build server accordingly.
Changes:
State: closed

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

No branches or pull requests

1 participant