Details
-
Type:
New Feature
-
Status: Open
-
Priority:
Major
-
Resolution: Unresolved
-
Component/s: None
-
Labels:None
Description
See comments. We will be distributing languages with Blesta that are generated from the DeepL API. We can salvage some parts of the translator for this project but it should be largely separate. We'll have to make API calls to get the translations, maintain them, and only fetch translations that have changed since the previous run.
older..
Amazon Translate is reported to be better than Google Translate as it uses machine learning. Add support for Amazon Translate to the translator so that it generates a complete translation of each language, though we may want to run it for each language manually to start so that we don't exceed the 2M character per month limit on the free tier to start.
https://aws.amazon.com/translate/
After a language has been "seeded", and we release an update, it should translate only the terms that are new or have changed.
This will allow us to have all languages translated 100% at all times. We can give priority to user translated strings that have confirmations, but I think we should have an Amazon Translate only download for each language for those that don't want to risk poor human translations given that anyone can sign up to translate.
Activity
Paul Phillips
created issue -
NOTE: DeepL is gaining some traction, if it'll work it might provide a better result than AWS https://www.deepl.com/en/translator
Looks like they have a developer API plan:
https://www.deepl.com/pro#developer
$5.49/mo + $25 per 1M characters. AWS is either $15 per 1M characters or $60 per 1M characters for their "custom translation" option that supposedly outputs things in a format we might be able to get to match existing files.
Paul Phillips
added a comment - - edited NOTE: DeepL is gaining some traction, if it'll work it might provide a better result than AWS https://www.deepl.com/en/translator
Looks like they have a developer API plan:
https://www.deepl.com/pro#developer
$5.49/mo + $25 per 1M characters. AWS is either $15 per 1M characters or $60 per 1M characters for their "custom translation" option that supposedly outputs things in a format we might be able to get to match existing files. We have an account now with DeepL, they have a PHP library at https://github.com/DeepLcom/deepl-php
Paul Phillips
added a comment - We have an account now with DeepL, they have a PHP library at https://github.com/DeepLcom/deepl-php Paul Phillips
made changes -
| Field | Original Value | New Value |
|---|---|---|
| Description |
Amazon Translate is reported to be better than Google Translate as it uses machine learning. Add support for Amazon Translate to the translator so that it generates a complete translation of each language, though we may want to run it for each language manually to start so that we don't exceed the 2M character per month limit on the free tier to start.
https://aws.amazon.com/translate/ After a language has been "seeded", and we release an update, it should translate only the terms that are new or have changed. This will allow us to have all languages translated 100% at all times. We can give priority to user translated strings that have confirmations, but I think we should have an Amazon Translate only download for each language for those that don't want to risk poor human translations given that anyone can sign up to translate. |
See comments. We will be distributing languages with Blesta that are generated from the DeepL API. We can salvage some parts of the translator for this project but it should be largely separate. We'll have to make API calls to get the translations, maintain them, and only fetch translations that have changed since the previous run.
older.. Amazon Translate is reported to be better than Google Translate as it uses machine learning. Add support for Amazon Translate to the translator so that it generates a complete translation of each language, though we may want to run it for each language manually to start so that we don't exceed the 2M character per month limit on the free tier to start. https://aws.amazon.com/translate/ After a language has been "seeded", and we release an update, it should translate only the terms that are new or have changed. This will allow us to have all languages translated 100% at all times. We can give priority to user translated strings that have confirmations, but I think we should have an Amazon Translate only download for each language for those that don't want to risk poor human translations given that anyone can sign up to translate. |
Supported languages https://developers.deepl.com/docs/resources/supported-languages
Some to consider for initial probably:
- Spanish
- German
- French
- Polish
- Dutch
- Turkish
- Chinese
- Greek
Eventually
- EN-GB British English
Paul Phillips
added a comment - - edited Supported languages https://developers.deepl.com/docs/resources/supported-languages
Some to consider for initial probably:
Spanish
German
French
Polish
Dutch
Turkish
Chinese
Greek
Eventually
EN-GB British English
After this task is completed, we should allow languages to be installed from Blesta that do not exist yet on the users local installation. We would interface with translate.blesta.com via an API to fetch available languages. Blesta would then download them (file permissions permitting) and install. The user wouldn't need to upload anything. We will need a task for this
We may want to keep Amazon Translate definitions separate, so that users can download a 100% machine translated version, or opt for a manual translation instead. Not sure, I guess it'll depend on how good the machine translations are.