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 addition to the problem with the current approach for getVoices() in Chrome for Android detailed in #12, we need to file a separate report about the list of languages itself.
A list of voices should only contain values that the user can use, but that's not the case currently in Chrome for Android. The list contains languages for which the voice pack hasn't been installed yet, which results in the TTS engine using English as a fallback.
In addition to the problem with the current approach for
getVoices()
in Chrome for Android detailed in #12, we need to file a separate report about the list of languages itself.A list of voices should only contain values that the user can use, but that's not the case currently in Chrome for Android. The list contains languages for which the voice pack hasn't been installed yet, which results in the TTS engine using English as a fallback.
Links:
Also reported in:
The text was updated successfully, but these errors were encountered: