lingva-translate
lingva-translate copied to clipboard
thedaviddelta
Multiple engines/backends
Currently lingva is based on google translate, which performs well but it is not the only choice. There are translators from microsoft, yandex and deepL as well as open source ones like apertium and https://libretranslate.com/
I think adding those engines would be great and is consistent with the goals of the project. Proprietary ones have privacy issues and user may want use them with a FOSS client and open source ones become promoted by being as an alternative here.
An abstraction on engines creates a path for contributors who want to add their favorite engine.
Hi and thank for your interest in this project.
Creating a multi-engine service was one of my firsts thoughts while imagine about creating Lingva, but I started by building it as an alternative frontend for GTranslate (and by the moment that's the goal for the project because I don't have much time right now). This is of course a thing I want to add to Lingva in the future, specially by using Yandex, DeepL & LibreTranslate if all three get to be able to be implemented, so I'll let the issue open and tag it with "enhancement" for tracking this upgrade for the future.
Regards, David.
https://github.com/crow-translate/crow-translate https://github.com/crow-translate/QOnlineTranslator
https://github.com/crow-translate/crow-translate https://github.com/crow-translate/QOnlineTranslator
Thanks for sharing this alternative! But as I pointed out in the other issue, the problem with QOnlineTranslator is that they use the GTranslate's public API, as well as Yandex's and Bing's ones, so it's not using the same approach as Lingva, which scrapes the service to avoid using Google services.
https://imtranslator.net/Translation-Comparison-for-Chrome.asp
I'm really interesting in this considering how much better Deepl is compared to Google Translate.
(also: would be really nice to see the translation results from all the providers at the same time)
