Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Add Google Translate as additional MT provider #1436

Closed
Tracked by #1928
, #2662
...
dkehne opened this issue May 17, 2022 · 12 comments · Fixed by #2637
Closed
Tracked by #1928
, #2662
...

Add Google Translate as additional MT provider #1436

dkehne opened this issue May 17, 2022 · 12 comments · Fixed by #2637
Assignees
@MizukiTemma
Labels
💡 feature New feature or request ❗ prio: medium Should be scheduled in the forseeable future. 😅 effort: medium Should be doable in <12h
Milestone
24Q1

Comments

@dkehne
Copy link

dkehne commented May 17, 2022 •
edited by svenseeberg

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
@dkehne dkehne added the 💡 feature New feature or request label May 17, 2022
@timobrembeck
Copy link
Member

timobrembeck commented May 17, 2022 •
edited

Duplicate of #1104

@timobrembeck timobrembeck marked this as a duplicate of #1104 May 17, 2022
@timobrembeck timobrembeck added ➿ duplicate This issue or pull request already exists and removed 💡 feature New feature or request labels May 17, 2022
@timobrembeck
Copy link
Member

Ok sorry, didn't notice the Intento part... this isn't supported yet.

@timobrembeck timobrembeck reopened this May 17, 2022
@timobrembeck timobrembeck changed the title Languages can be translated directly with our integreat-cms (Intento & DeepL) Support automatic translations via Intento May 17, 2022
@timobrembeck timobrembeck added 💡 feature New feature or request and removed ➿ duplicate This issue or pull request already exists labels May 17, 2022
@timobrembeck timobrembeck added this to the Backlog milestone May 17, 2022
@timobrembeck timobrembeck added ⁉️ prio: low Not urgent, can be resolved in the distant future. 😅 effort: medium Should be doable in <12h labels May 17, 2022
@svenseeberg svenseeberg modified the milestones: Backlog, 22Q3 Jun 7, 2022
@svenseeberg svenseeberg added ‼️ prio: high Needs to be resolved ASAP. and removed ⁉️ prio: low Not urgent, can be resolved in the distant future. labels Jun 7, 2022
@dkehne
Copy link
Author

dkehne commented Jul 21, 2022

@ulliholtgrave @timoludwig prio high can be removed. don't focus that in the next 2 month...

@ulliholtgrave ulliholtgrave added ❗ prio: medium Should be scheduled in the forseeable future. and removed ‼️ prio: high Needs to be resolved ASAP. labels Jul 21, 2022
@ulliholtgrave ulliholtgrave modified the milestones: 22Q3, 22Q4 Jul 21, 2022
@ulliholtgrave ulliholtgrave mentioned this issue Sep 5, 2022
Closed
@JoeyStk JoeyStk self-assigned this Sep 5, 2022
@JoeyStk JoeyStk removed their assignment Sep 28, 2022
@ulliholtgrave ulliholtgrave modified the milestones: 22Q4, 23Q1 Nov 4, 2022
@JoeyStk JoeyStk modified the milestones: 23Q1, Backlog Nov 30, 2022
@timobrembeck timobrembeck added the ⁉️ prio: low Not urgent, can be resolved in the distant future. label Jan 14, 2023
@charludo charludo mentioned this issue Feb 6, 2023
Closed
@svenseeberg svenseeberg changed the title Support automatic translations via Intento Support automatic translations with other providers Oct 4, 2023
@svenseeberg svenseeberg modified the milestones: Backlog, 23Q4 Oct 4, 2023
@svenseeberg svenseeberg changed the title Support automatic translations with other providers Concept automatic translations with additional providers Oct 4, 2023
@svenseeberg svenseeberg added ❗ prio: medium Should be scheduled in the forseeable future. and removed ⁉️ prio: low Not urgent, can be resolved in the distant future. labels Oct 4, 2023
@osmers
Copy link

osmers commented Oct 31, 2023

@dkehne Did we already decide to implement Google Translate or are we still in the process of deciding?
I think we can already create another issue regarding the "additional attribute that defines the preferred automatic translation provider", right?

@sarahsporck
Copy link
Contributor

As this ticket is not yet well defined this ticket will be moved into 24Q1 for now.

@sarahsporck sarahsporck modified the milestones: 23Q4, 24Q1 Nov 7, 2023
@svenseeberg svenseeberg modified the milestones: 24Q1, 24Q2 Dec 6, 2023
@MizukiTemma MizukiTemma mentioned this issue Dec 11, 2023
Closed
@dkehne dkehne mentioned this issue Dec 11, 2023
Open
@svenseeberg svenseeberg modified the milestones: 24Q2, 24Q1 Dec 13, 2023
@dkehne
Copy link
Author

dkehne commented Jan 16, 2024

@MizukiTemma Google Translate Prio 1, Microsoft Translate Prio 2. Based on DeepL-quality-Report: https://www.deepl.com/en/quality.html

@dkehne
Copy link
Author

dkehne commented Jan 16, 2024

information-14-00574-g003
Altough in general scorings Google seems to be a bit better.

@JoeyStk JoeyStk changed the title Concept automatic translations with additional providers Add Google Translate as additional MT provider Jan 16, 2024
@JoeyStk JoeyStk mentioned this issue Jan 16, 2024
Open
@MizukiTemma
Copy link
Member

MizukiTemma commented Jan 16, 2024 •
edited

☝️Keep #2586 in mind before/when implementing this issue.

@MizukiTemma MizukiTemma self-assigned this Jan 31, 2024
@MizukiTemma MizukiTemma mentioned this issue Feb 5, 2024
Merged
@dkehne
Copy link
Author

dkehne commented Feb 6, 2024

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?!

@MizukiTemma
Copy link
Member

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 GOOGLE_TRANSLATE_VERSION

@MizukiTemma MizukiTemma mentioned this issue Feb 15, 2024
Open
23 tasks
@svenseeberg svenseeberg mentioned this issue Mar 2, 2024
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@MizukiTemma MizukiTemma

Labels
💡 feature New feature or request ❗ prio: medium Should be scheduled in the forseeable future. 😅 effort: medium Should be doable in <12h
Projects
None yet
Milestone
24Q1
Development

Successfully merging a pull request may close this issue.

Add Google Translate as MT provider digitalfabrik/integreat-cms
8 participants
@dkehne @svenseeberg @ulliholtgrave @timobrembeck @sarahsporck @osmers @JoeyStk @MizukiTemma