Translators for a Linguist browser extension.
Directory translators
contains files with custom translators implementations.
This modules is not embedded to a Linguist because not ready to production use, may works not stable or need configuration, like API keys.
The purpose of this list is to provide for users an alternative translators.
If you have project about text translation, you can add translator with bindings for your API to a current directory and create pull request. Read custom translators API docs to create bindings for your translation service
See custom translators guide in Linguist repository.
- LibreTranslator [github] - machine translation project that may be deployed locally (read more in Offline translation manual)
- TartuNLP [github] - machine translation engine developed by the NLP lab at the University of Tartu
- LingvaTranslator [github] - google translator API proxy with list of public instances
A directory translators/generated contains code of translators from stable libraries, that ready to use in Linguist and in browser at all.
Generated code may looks bloated, but this code have support.
- Alternative Google translator implementation. Try it if you are not satisfied with embedded google translator
- DeepL - translator for service deepl.com. You have to insert your personal API key on bottom of translator code
- WARNING: with DeepL you pay for each character of translated text. If you will use DeepL translator with Linguist to translate pages, it can cost a fortune, because random wikipedia page contains 88267 characters, so you will pay 1.8 EUR (
0.00002 * 88267
) per ONE wikipedia page
- WARNING: with DeepL you pay for each character of translated text. If you will use DeepL translator with Linguist to translate pages, it can cost a fortune, because random wikipedia page contains 88267 characters, so you will pay 1.8 EUR (
To build translators:
- install packages
npm install
- build with
npm run build
If you found bugs, please create issue with detailed description problem you have