Feature/deep translator integration #303
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
PR Checklist
docs
is updatedDescription of changes
This PR introduces a additional translatros to be used with the Translator superclass. Check the new falvours for "libre", "mymemory", "microsoft", "yandex" translators. Note that keys are required for "yandex" and "microsoft" and that these are currently skipped in tests. The other two have quite strict limits on the number of requets /minute and/or /day. This them unsuitable for proper usage at this stage. Thay are working though.
Some translators like "pons" or "linguee" only translate individual words and are not supported. Also, the "qcri" translator mainly support arabic which might not be relevant at this point in time and is excluded here.
For testing the check of available tokens has been further abstracted.
Technical details
Adresses #115 and ticks the checkpoint on
Implement all other translators
.Additional context