-
```
It cannot be used for odata and azure services, it seems that only the "already
almost deprecated" way has been implemented.
It should implement the actual Windows Azure api for translate, sinc…
-
```
It cannot be used for odata and azure services, it seems that only the "already
almost deprecated" way has been implemented.
It should implement the actual Windows Azure api for translate, sinc…
-
Please ensure you have given all the following requested information in your report.
#### Please select the affected platforms
- [x] Android Studio
- [ ] IntelliJ IDEA
#### Please select the…
-
```
It cannot be used for odata and azure services, it seems that only the "already
almost deprecated" way has been implemented.
It should implement the actual Windows Azure api for translate, sinc…
-
```
It cannot be used for odata and azure services, it seems that only the "already
almost deprecated" way has been implemented.
It should implement the actual Windows Azure api for translate, sinc…
-
https://www.microsoft.com/en-us/translator/trial.aspx
on the page there is written that it could be done by using the “category=generalnn” in your Translator Text API call
-
from translatepy.translators.microsoft import MicrosoftTranslate
t = MicrosoftTranslate()
result = t.text_to_speech("Hello", 65, "male", "eng")
Traceback (most recent call last):
File "D…
-
```
It cannot be used for odata and azure services, it seems that only the "already
almost deprecated" way has been implemented.
It should implement the actual Windows Azure api for translate, sinc…
-
```
It cannot be used for odata and azure services, it seems that only the "already
almost deprecated" way has been implemented.
It should implement the actual Windows Azure api for translate, sinc…
-
```
It cannot be used for odata and azure services, it seems that only the "already
almost deprecated" way has been implemented.
It should implement the actual Windows Azure api for translate, sinc…