-
Notifications
You must be signed in to change notification settings - Fork 783
VoiceManager fails to find suitable voice #2352
Comments
Is there any plan to add other lenguages in case they are supported? As far as I know VoiceRSS supports multiple lenguages. |
The voice infrastructure supports ANY language, it all just depends on what voices are available. Currently, the VoiceRSS TTS has support for de and en, but this can be easily extended to all 26 languages offered by VoiceRSS (@JochenHiller, correct me, if I am wrong). |
@Jaghova Yep, there are more languages, which I planned to add. The initial contribution was done in just 2 evenings, I wanted to add first test cases before adding more features. But sure, I will add all supported languages of VoiceRSS extension soon. @kaikreuzer about the reported issue: VoiceRSS extension does register languages with both country and region code (e.g. de_DE). So I did not run into that issue. Just as an idea which I came up during testing and demoing that feature: the "say" command could support an option to specify the locale, e.g. "say --locale "de" "Hallo Welt"? |
The say() command in rules supports defining a voice that should be used - through this, the locale is also directly chosen. I would think that this is good enough (and we could add this option to the console say command as well, yes), since in most cases, you really want to chose the voice that is used. |
I actually think that this problem might be fixed through the commented out code in VoiceManager - unfortunately, this feature is only available in Java 8, so this code cannot be enabled (yet)... |
Is it now possible to activate the language output in german? |
…clipse-archived#2352 Signed-off-by: Henning Treu <henning.treu@telekom.de>
There is some problem with the selection of the right voice to use in VoiceManager.
If e.g. MaryTTS is installed, you have:
Calling
results in
When the locale (in Configuration->System) is set to "de" instead of "de_DE", TTS works as expected.
The text was updated successfully, but these errors were encountered: