vlastdoloy
Same

Reconnected from wifi to the operator (Beeline), Google earned.

Google is again trying to block the use of their unofficial API (which is intended only for translate.google.com). In fact, after a few translations, they are firing that requests are not coming from translate.google.com, and temporarily block IP. Therefore, it works, it does not work. And so the same connection to another network helps for a while. There is a workaround, I hope to release before the end of the month. But the problem is that Google can close it too and everything will break again.

Because Google stopped working, a lot of people started using the MS translator. And there I have a limit of 2 million characters per month (for all users). Now I have to work again, because The limit is reset to 25th.

Yandex should work. If an error pops up - write here or to me in PM.

Version1.3.0 : DEB for Nokia N9 , RPM for Sailfish OS ARMv7 (Jolla Phone) , RPM for Sailfish OS x86 (Jolla Tablet) .

Changes:

• Google Translator: Attempting to fix (bypass) the translation error "Service unavailable".
  
• Yandex.Dictionaries: Fixed "SSL handshake failed" on some phones.
  
• Now real SSL connection errors are shown, instead of just "SSL handshake failed".
  
• Added application analytics. When you first start it will show a request for consent.
  
• When Paste'n'Translate is activated, the buttonInsertwill replace the current text with the text from the buffer; when the Paste'n'Translate is inactive, the buttonInsertjust paste text from the buffer, in addition to the existing one.
  
• Sailfish OS: The setting for the selected interface language was saved in the wrong place.
  
• Nokia N9: Fixed "SSL handshake fail" error when checking for updates.
  
• New interface languages: Bulgarian, Catalan, Polish, Finnish and Swedish.

Version1.3.1 : DEB for Nokia N9 , RPM for Sailfish OS ARMv7 (Jolla Phone) , RPM for Sailfish OS6 (Jolla Tablet) .

Changes:

• Google Translate: Bypassing the "server replied: Forbidden" error.
  
• New interface languages: Hungarian and Portuguese.

Google translator does not work again

About an hour ago, updates appeared on the githaba, in particular, bypassing the google transport unit.
Once again I express my gratitude to the author)
I am sure that later on the official update, an official update will be posted here, but for those who are impatient and need to "go straight ahead" - keep debike.


taot_1.3.1_armel.deb(202 KB)

Finally, there was a time to fix (once again bypass) the Google service. How long will live - I do not know.

Version1.3.2 : DEB for Nokia N9 , RPM for Sailfish OS ARMv7 (Jolla Phone) , RPM for Sailfish OS x86 (Jolla Tablet) .

Changes:

• Google Translator: Changed API server. Must fix the "500 Forbidden" error.
  
• Some interface translations have been updated.

Changelog:
taot (1.3.3) unstable; urgency = low
* Source and target translation languages ​​were updated for all services.
* Add root CA certificates for Google Translate and Microsoft Translator
services to avoid SSL handshake errors due to untrusted root
certificate.
* A slight rearrangement of menus.


taot_1.3.3_armel (1) .deb(269.8 KB)

Version1.3.4 : DEB for Nokia N9 , RPM for Sailfish OS ARMv7 (Jolla Phone), RPM for Sailfish OS x86 (Jolla Tablet).

Changes:

• Microsoft Translator: Microsoft plans to close the DataMarket API on 04/04/2017. TAO Translator now uses the Azure Cognitive Services API.
  
• Some interface translations have been updated.

Does the voice translation program not support?

Version1.3.5 : DEB for Nokia N9 , RPM for Sailfish OS ARMv7 (Jolla Phone), RPM for Sailfish OS x86 (Jolla Tablet).

Changes:

• Google Translator: Fixed SSL connection error on some platforms caused by unreliable root certificate.
  
• Source and target translation languages ​​were updated for all services.
  
• Nokia N9: Workaround "SSL handshake failed" error when checking for updates.
  
• New interface language: Dutch (Belgium).
  
• Updated some interface translations.

Unfortunately not.There are planslosing the translation on the services that support it, but when I have time to implement it, I have no idea.