-
-
Notifications
You must be signed in to change notification settings - Fork 659
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
Please default ESpeak NG's voice role to "Chinese (Mandarin, latin as Pinyin)" for Chinese to fix #12952 #13572
Comments
Is this then, not also an issue you need to report to the Espeak list as
well?
Brian
|
@Brian1Gaff |
Still thanks for your suggestion, I'll make the same request in the ESpeak repo if possible. |
|
Note, the default / preference for the voice for a certain language code is controlled by espeak-ng. |
hi @feerrenrut Unfortunately #12950 doesn't change anything for that. Thanks |
Hi, |
Hi guys, If this commit is merged, and espeak-ng/espeak-ng#1044 is closed, then this issue can also be closed after updating eSpeak. |
Can you let us know when we can update eSpeak to close this issue |
@seanbudd |
@seanbudd |
@cary-rowen - 2022.3beta is well and truly closed to new features. We will try to update eSpeak again for 2022.4 |
Is your feature request related to a problem? Please describe.
#12952 makes ESpeak completely unusable for Chinese users. This is a disaster for beginners who cannot use Windows OneCore.
Describe the solution you'd like
After testing, setting the voice role of ESpeak NG to "Chinese (Mandarin, latin as Pinyin)" can temporarily solve #12952 .
The word "temporarily" is used because the English pronunciation of "Chinese (Mandarin, latin as Pinyin" is less vivid than the current default "Chinese (Mandarin, latin as English)".
But this solution can get rid of the dilemma of not being able to use ESpeak NG at all.
Describe alternatives you've considered
The best solution is to solve #1028 by ESpeak.
Make "Chinese (Mandarin, latin as English)" can speak Chinese correctly.
Additional context.
I think this question is urgent enough, especially for beginners of nvda.
The text was updated successfully, but these errors were encountered: