-
Notifications
You must be signed in to change notification settings - Fork 38
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add Google Translate as additional MT provider #1436
Comments
|
Ok sorry, didn't notice the Intento part... this isn't supported yet. |
@ulliholtgrave @timoludwig prio high can be removed. don't focus that in the next 2 month... |
@dkehne Did we already decide to implement Google Translate or are we still in the process of deciding? |
As this ticket is not yet well defined this ticket will be moved into 24Q1 for now. |
@MizukiTemma Google Translate Prio 1, Microsoft Translate Prio 2. Based on DeepL-quality-Report: https://www.deepl.com/en/quality.html |
☝️Keep #2586 in mind before/when implementing this issue. |
It's really hard to tell at the moment if we go with the Cloud Translate API Basic (~costs around 20$/1m chars) or Cloud Translate API Advanced (~costs around 80$/1m chars). The advanced API can be trained with our data from the .tmx-Files. Hopefully you can implement the API without forcing us to make this decision too early. I guess we need somehow both options to compare the results...So maybe go for the Basic-API first and then mabye add the API-Advanced as a second API in the test cms only?! |
The implementation was changed so both basic (v2) and advanced (v3) versions can be used, by specifying the variable |
Motivation
Integreat and associated translations should take less time and process to maintain. Also it leads to lower costs of the whole project.
Proposed Solution
We want to support additional automatic translation providers, for example Google and Microsoft. Each language should get an additional attribute that defines the preferred automatic translation provider.
The scope of this issue is to create additional issues that define the implementation steps.
Alternatives
If TM-Connecting is too difficult at the start we could begin with the glossary (term database) and the enhance it with TM on a later date.
Additional Context
The text was updated successfully, but these errors were encountered: