Google translate - no pronunciation, Yandex translate - doesn't work at all

[iG0R]

Hi.
Could you, please, fix issues mentioned in the title of the topic.
Also, could it be possible to add such an option which allows to show an instant translation after selecting text without holding any additional keys?
And it would be more convenient to see transcription part in translation pop-up window on the new line.
One more question - how could I specify the position of the pop-up window relative to the selected text or cursor?
Thanks in advance.

PS. Firefox 83.

[Andrey Shemetov]

Issue #68 was marked as a duplicate of this issue.

[Andrey Shemetov]

1. Pronunciation is actually working for me, presumably some connectivity issues on your side. For instance corporate networks are blocking access to Google translate.
2. Yandex translate - got a message ‘{"code":408,"message":"Maximum monthly translated text volume exceeded"}', looks like someone stole keys and abused translation API. I’ll add a workaround for Yandex dictionary (it uses separate set of keys), but Yandex translate may require brand new ones and there is no guarantee that keys will be not stealing again.
3. Will add an option to show transcription on the separate line
4. Instant translation will transform SelectionSK to translation extension, there are plenty of them. At the end it is not a big deal to hold a Ctrl key.
5. Popup position selected automatically, there are no immediate plans to change that.

‌

[Andrey Shemetov]

Well issue is different: 'С 31 июля 2020 года вы сможете бесплатно переводить 50 000 символов в день, а с 15 августа 2020 года мы закрываем доступ к бесплатному API Яндекс.Переводчика.'

I’ll remove Yandex translate if will not find a way to get it for free.

[iG0R]

1. Hm, strange things happen - recently other translation add-ons ceased to playback pronunciations too, except some peculiarities, e.g. in “Translate Man Plus” https://addons.mozilla.org/en-US/firefox/addon/translate-man-plus/ pronunciation only works in English->English direction of translation, in all other directions (e.g. Chinese->English or English->Chinese) it doesn’t work. And what is weird in English->English direction there are 2 different types of pronunciation. Maybe Google Translate “znowu popierdolilo“.
2. There is “QTranslate“ https://forum.ru-board.com/topic.cgi?forum=5&topic=35038&start=3340 in which Yandex Translator works well. Perhaps you could find solution there?
3. Thank you Small clarification - please, place transcription under the text to which this transcription relates to.
4. Yes, there are plenty, but SelectionSK is the best I asked only for the tiny checkbox or radio button near “Hold Ctrl for instant translation“ which allows to appear pop-up window instantly after selecting text. Sometimes it’s really a big deal while trying to use some functionality of big PC on TabletPC or on a laptop with touchscreen. To avoid some inconveniences while using this option it’s worth to add “Menu/Pane“ to the title of this window.
5. OK, I’m looking forward for this feature in the future releases.
6. And one more oddity - while using SelectionSK on TabletPC or laptop with touchscreen each tap is perceived by the computer as an attempt of selecting text resulting in popping of floating icons of other extensions or programs, e.g. floating icon of QTranslate.

‌

[iG0R]

Also would really like to see the following functionality:

7. Selecting different Pronunciation modes:

• Pronounce when hovering over speaker icon
• Pronounce when click
• Automatic pronunciation while pop-up window appears

8. Multiple languages support with optional multidirectional translation, i.e.

(1) lang - Chinese (English)

(2) lang - English (Chinese, Russian, Japanese)

(3) lang - Russian (English, Chinese)

If selected text is in Chinese translate it to English only.

If selected text is in English translate it to Chinese, Russian and Japanese.

If selected text is in Russian translate it to English and Chinese.

[iG0R]

Regarding clause #6 - each tap evokes selection of the current page title that leads to popping of the floating icons of other extensions or programs.

[iG0R]

Here is why pronunciation doesn’t work:

18:36:05.216 XHRGEThttps://clients5.google.com/translate_a/t?client=dict-chrome-ex&sl=auto&tl=en&q=error
[HTTP/2 200 OK 340ms]

18:36:05.610 Some cookies are misusing the recommended “SameSite“ attribute 6
18:36:06.980 GEThttps://translate.google.com/translate_tts?ie=UTF-8&q=error&tl=en&total=1&idx=0&textlen=5&client=t&tk=345388.345388
[HTTP/2 403 Forbidden 43ms]

GET
https://translate.google.com/translate_tts?ie=UTF-8&q=error&tl=en&total=1&idx=0&textlen=5&client=t&tk=345388.345388
Status403
Forbidden
VersionHTTP/2
Transferred853 B (0 B size)

alt-svc
    h3-29=":443"; ma=2592000,h3-T051=":443"; ma=2592000,h3-Q050=":443"; ma=2592000,h3-Q046=":443"; ma=2592000,h3-Q043=":443"; ma=2592000,quic=":443"; ma=2592000; v="46,43"
cache-control
    private, max-age=86400
content-length
    0
content-type
    audio/mpeg
date
    Thu, 10 Dec 2020 16:36:08 GMT
expires
    Thu, 10 Dec 2020 16:36:08 GMT
server
    HTTP server (unknown)
set-cookie
    SIDCC=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx; expires=Fri, 10-Dec-2021 16:36:08 GMT; path=/; domain=.google.com; priority=high
set-cookie
    __Secure-3PSIDCC=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx; expires=Fri, 10-Dec-2021 16:36:08 GMT; path=/; domain=.google.com; Secure; HttpOnly; priority=high; SameSite=none
x-content-type-options
    nosniff
X-Firefox-Spdy
    h2
x-xss-protection
    0

Accept
    audio/webm,audio/ogg,audio/wav,audio/*;q=0.9,application/ogg;q=0.7,video/*;q=0.6,*/*;q=0.5
Accept-Language
    en-US,en;q=0.5
Cache-Control
    no-cache
Connection
    keep-alive
Cookie
    NID=204=xxxxxxxxxxxxxxxxx
    1
Host
    translate.google.com
Pragma
    no-cache
Range
    bytes=0-
Referer
    <https://translate.google.com/>
TE
    Trailers
User-Agent
    Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:83.0) Gecko/20100101 Firefox/83.0

18:36:07.030 ash: onPlayError common.js:51:7
18:36:07.030 HTTP load failed with status 403. Load of media resource https://translate.google.com/translate_tts?ie=UTF-8&q=error&tl=en&total=1&idx=0&textlen=5&client=t&tk=345388.345388 failed. _generated_background_page.html
18:36:07.032 Uncaught (in promise) DOMException: The media resource indicated by the src attribute or assigned media provider object was not suitable.
18:36:07.988 GEThttps://translate.google.com/translate_tts?ie=UTF-8&q=error&tl=en&total=1&idx=0&textlen=5&client=t&tk=345388.345388
[HTTP/2 403 Forbidden 43ms]

18:36:08.035 HTTP load failed with status 403. Load of media resource https://translate.google.com/translate_tts?ie=UTF-8&q=error&tl=en&total=1&idx=0&textlen=5&client=t&tk=345388.345388 failed. _generated_background_page.html
18:36:08.036 ash: onPlayError common.js:51:7
18:36:08.037 Uncaught (in promise) DOMException: The media resource indicated by the src attribute or assigned media provider object was not suitable.

[iG0R]

As it turned out pronunciation issue was caused due to incorrect “client“ value.

While using “client=dict-chrome-ex” there is no issues oсcure.

I figured out for some unknown reason using “client=at“ result in all issues with google translate API in my system at the same time “gtx“ and “dict-chrome-ex“ work OK.

[Andrey Shemetov]

Sounds like an issue with your (or corporate) firewall. Anyway, I’ll change to 'gtx' because it is used for Google translation anyway.

[iG0R]

It’s better to change to “dict-chrome-ex“ because answers from the google translate server sometimes are too different between “gtx“ and “dict-chrome-ex“ and include more information if they are from the latter.

And it’s not an issue on my side but from the google translate server itself, you can check it, there are many discussions in the internet https://www.google.com/search?newwindow=1&q=translate+google+Our+systems+have+detected+unusual+traffic+from+your+computer+network.

[Andrey Shemetov]

7. Maybe will add in the future. Not sure if such feature is really useful.

8. There are no plans to add a support for multiple languages unless there will be a way to present it to user in a clear way. Current proposal looks bulky and will over-complicate UI. Instead, SelectionSK allows to select origin or destination language right on the translation window or even swap languages.

[Andrey Shemetov]

Version 5.1 released, covers most of the reported issues.