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
Click play button, each time you will heart nothing
A clear and concise description of what the bug is, and what you expected to happen.
In this case, reproduce /soso/ but really I want Text to Speech can reproduce all phonemes, right now it only support a small IPA subset
Also the bot is closing issues that DON'T REQUIRE A REPRODUCTION URL, fix your workflow, I'm providing a URL with information provided in the issue
A clear and concise description WHY you expect this behavior, i.e., was it a recent change, there is documentation that points to this behavior, etc. **
Because I wrote an IPA reader, and if Text to Speech doesn't support it, I can't use Text to Speech
The text was updated successfully, but these errors were encountered:
Issue was opened with an invalid reproduction link. Please make sure the repository is a valid, publicly-accessible github repository, and make sure the url is complete (example: https://github.com/googleapis/google-cloud-node)
Please make sure you have searched for information in the following guides.
A screenshot that you have tested with "Try this API".
Link to the code that reproduces this issue. A link to a public Github Repository or gist with a minimal reproduction.
https://gist.github.com/jefer94/c98a9fb64987cf135b6df524b6de5056
A step-by-step description of how to reproduce the issue, based on the linked reproduction.
A clear and concise description of what the bug is, and what you expected to happen.
In this case, reproduce /soso/ but really I want Text to Speech can reproduce all phonemes, right now it only support a small IPA subset
Also the bot is closing issues that DON'T REQUIRE A REPRODUCTION URL, fix your workflow, I'm providing a URL with information provided in the issue
A clear and concise description WHY you expect this behavior, i.e., was it a recent change, there is documentation that points to this behavior, etc. **
Because I wrote an IPA reader, and if Text to Speech doesn't support it, I can't use Text to Speech
The text was updated successfully, but these errors were encountered: