Translator fails to display correctly
Screen capture, OCR and translation tool
Brought to you by:
onemoregres
Whenever I try to translate anything, it will take a very long time to translate, and then when it finally does it either displays the same text I screen captured, or it displays garbage.
However, if I enable debug mode, it will successfully translate in the translator window, but only if I use bing or google. Yandex displays this screen https://i.imgur.com/lLXw1Bv.png
Try to update the translation scripts first (ticket #3).
Also if you see similar messages you can try to manually translate something with the same service (https://translate.yandex.ru/ , https://translate.google.com/ , etc) and solve captcha there. It might then whitelist you ip and allow translator to work.
After successfully updating, it was finally able to display the translation on the overlay. I dropped the "Max Translation time" to 5 seconds and it's quite fast. If I try translating with yandex only, it still fails. I don't think I can solve the captcha unless I install cyrillic
Last edit: FragmentalStew 2020-01-14
The debug mode window doesn't load images at all. Saying 'manual translate' I meant something like 'translate the same thing in a normal browser'.
And I don't think Yandex is so cruel and requires everyone to solve cyrillic captcha :D
When I went to yandex.ru in my normal browser, it gave my a cyrillic captcha. I managed to keep cycling the captchas until it gave me one without cyrillic and I was able to solve it, but then yandex only worked once or twice in ScreenTranslator, then it quit working again. I suspect that people having trouble getting ScreenTranslator to work either needed to update, or they were unknowingly having this problem with yandex, or another translator.
Deepl also wasn't working for me, but that might be because I was trying to translate a language it doesn't support. I was also having a similar but different problem with papago. It times out, but in the debug mode, it displays the page, I just have to click "translate" manually.
Last edit: FragmentalStew 2020-01-15
Thanks for the details.
Yandex is unlikely to be fixed by updating the translation script. It seems the only solution is to allow to solve captcha from debug mode or its alternative.
If you have some working translators, I'll look at papago a little later (I have many postponed tasks :) ).
Finally tested papago. It worked fine for me. At least in the question of manual 'translate' click...
I think papago was failing on me because my timeout was too low, and it was taking longer than the other translations services
Starting from 3.0.0 the app uses another translation engine, so this issue is no more actual. Open the new one (preferrable on github) if you have issues with a new app version