Continuous automated translation weirdness

Created on 19 December 2019, about 5 years ago
Updated 8 November 2023, about 1 year ago

I have configured the site to automatically translate content using DeepL. The deepl provider is set to "auto accept finished translations". This works (mostly) fine, but I have noticed a strange behaviour related to "needs translation".

  1. When no translation exists, translation is generated on edit.
  2. When translation already exists, new translation is only generated if the "Flag other translations as outdated" is set.
  3. When a new translation is added by DeepL, the "this translation is outdated" flag is not removed.

Ideally, I woudl like to have following configuration options:

  1. "Flag other translations as outdated" publishing option. analogous to "Create new revision"
  2. "Auto update translation status" in addition to "Auto accept finished translations" in the Deepl provider configuration. Or globally.

When both these options are set, the default would be to ask the Deepl to translate on every edit and the "outdated" flag would be automatically removed afterwards.

Feature request
Status

Closed: outdated

Version

2.1

Component

Code

Created by

🇦🇹Austria Deno

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

Production build 0.71.5 2024