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
In short: Google's text-to-speech services do not recognise zh_HK for Cantonese but do recognise yue_HK.
In long:
zh_HK as far as I know refers to 書面語 which is the Hong Kong variant of Standard Written Chinese using Cantonese pronunciation.
It is distinct from Hong Kong Cantonese, which is called 粵語 and I believe uses yue_HK.
Both use Cantonese pronuncation, so the distinction is unnecessary except that in Android with Google's speech services' Cantonese pronunciation it is necessary that it is yue_HK else it will not be able to find a compatible text-to-speech generator.
What I do to get around this is I go into awesometts/service/languages.py and change zh_HK to yue_HK and it works.
I suggest that zh_HK be replaced with yue_HK, or even better that both are "merged" so to speak so that both codes are tried before giving up on finding a voice.
The text was updated successfully, but these errors were encountered:
In short: Google's text-to-speech services do not recognise
zh_HK
for Cantonese but do recogniseyue_HK
.In long:
zh_HK
as far as I know refers to 書面語 which is the Hong Kong variant of Standard Written Chinese using Cantonese pronunciation.It is distinct from Hong Kong Cantonese, which is called 粵語 and I believe uses
yue_HK
.Both use Cantonese pronuncation, so the distinction is unnecessary except that in Android with Google's speech services' Cantonese pronunciation it is necessary that it is yue_HK else it will not be able to find a compatible text-to-speech generator.
What I do to get around this is I go into awesometts/service/languages.py and change zh_HK to yue_HK and it works.
I suggest that zh_HK be replaced with yue_HK, or even better that both are "merged" so to speak so that both codes are tried before giving up on finding a voice.
The text was updated successfully, but these errors were encountered: