Add checkbox Automatic translation for outdated translation on page form

[ulliholtgrave]

Motivation

In the daily work of the municipalities the normal workflow includes updating the german content and directly wanting to translate them to other languages. Therefore, our automatic translation workflow should include a possibility to trigger automatic translations directly in the page form for now outdated translation.

Proposed Solution

Add another checkbox below/above (TBD) "minor_edit" that is exclusive to "minor_edit". If it is checked and the page gets updated, all translations that would be outdated and are supported by DeepL are automatically translated.

The result would be a manual created german translation and up-to-date translations in other languages.

The translation budget needs to be considered for the translation.

Additional Context

Related to:

• Build page tree for new section "Translations" #1727
• Design interface for automatic translations #1663

This blocks:

• Simplify the DeepL translation process for events & locations #1459
• Add possibility to automatically update Easy German translations via SUMM.AI from page form #2110

[nikolahoff]

@ulliholtgrave if the budget for translations is not sufficient is it possible
a) to show an info: "Your budget is not sufficient. You want to translate 123 words but you only have credits for 56 words."
b) to disable the "Update" button in that case?

[ulliholtgrave]

@nikolahoff Yes, this is possible.

However, We should consider the case when a user is trying to translate into 5 languages but his budget only allows translations for 3. In this case we would stop the translation process after 3 and inform the user about 2 missing languages due to insufficient funds. Does that sound like a reasonable solution for you?

[nikolahoff]

Sounds good. Can we show an info-box in that case?

[ulliholtgrave]

Yes, My suggestion would be a redirect to the current page and an info message on the top describing the issue and a list of skipped translations.

[osmers]

@ulliholtgrave @nikolahoff how do we deal with the possible issue that Kommunen will call us and say that, had they known, they would have chosen different languages to translate the text into? Not sure how probably this is, since the budgets should be large enough. Just wanted to alert to the possibility...maybe we can stop the process before anything is translated, saying that the budget would only be large enough for x languages, and to please go to the settings and choose the ones they want?

[ulliholtgrave]

@osmers I guess we addressed this with the priority setting, right? If we set up the automatic translation for them we should highlight the reason for this setting and they should think about how they want to configure their AT process. However, I guess we can still add a warning if they try to translate more text then their budget (with the possibility to abort the process).

[osmers]

@ulliholtgrave maybe @dkehne can give his input here bcs he was not a fan of our prioritising - it would be too confusing.

[timobrembeck]

We're talking about a single page here, right?
I doubt that the difference between one single page being translated into language X but not into language Y makes such a huge difference.
If they really cannot live with a partially translated page, they can also manually copy the content into the DeepL UI to finish the missing languages by hand.
I doubt the programming effort is justified by such an edge case which does not have drastic implications.

[osmers]

I doubt the programming effort is justified by such an edge case which does not have drastic implications.

Makes sense - let's keep it simple then. Might be something we need to fix in case it happens often, but I highly doubt it. In theory at least, the 50.000 words should be enough to translate Aktualisierungen.

[osmers]

@charludo maybe you can post the current design here for the checkbox and explain the idea of language selection?

[charludo]

@osmers yes, here's the current state:

1. initial situation when opening a page(/event/poi) in the editor:
   

2. checking "automatic translation" opens this form:
   

By default, only existing translations are checked (the behaviour originally requested in this issue), but the user has the option to also create new, non-existent translations.

[osmers]

Thanks a lot - that looks very cool I think :)