I'm rising this issue up again. Please could you anyone with proper permissions level to check the project and/or component settings regarding the translation propagation?

All the f40 components are at 0%.

If there is a reason why propagation is turned off, I'm willing to document a sort of workaround... probably through an offline translation...?

Propagation is enabled between these components, however propagation happens as soon as you save a translation and it doesn't apply automatically for future components. What is happening is that f40/* components are being added after translation being propagated and then these translation contributed are shown as suggestion due to Translation Memory.

Also Fedora translation scripts don't merge translations from existing components into newly created PO. Implementing this would be rather dangerous as this would easily cause merge conflicts all over Fedora Weblate.

One solution is to enable Automatic translation plugin. (see documentation).

The Automatic translation plugin pre-fills translation of all messages that have same source string. It has project-wide effect (i.e. enables for all of its components) and It can be configured to use machine translation or translation memory (TM). We have no machine translation set, and probably what you want is TM.

What you are probably asking is to set this plugin with mode "translated" (See docs about it): once the new release is available for translation, Weblate will copy translation from TM into the new translation file.

The downside of this plugin with mode=translated is that this is an unattended translation, no translator will manually mark as OK. Do we want that?

Also, no other fedora-docs-l10n project (i.e. Weblate translation project) has "Automatic translation" plugin enabled (for better or for worse). Do we want to have this difference between other projects? Or do we want to enable in other projects as well?

Really thank you for the overview.

What is happening is that f40/* components are being added after translation being propagated and then these translation contributed are shown as suggestion

Understood. :)

The Automatic translation plugin pre-fills translation of all messages that have same source string...

Yes, probably I would like to have this working. And I am open to help to think it through (pros and cons).

From the point of a 'poor' translator I would like to get rid of the must to click 250 times the accept suggestion button whenever a new Fedora version is released. That is the goal I would love to achieve.

probably what you want is TM

Yes.

Also, no other fedora-docs-l10n project (i.e. Weblate translation project) has "Automatic translation" plugin enabled (for better or for worse). Do we want to have this difference between other projects? Or do we want to enable in other projects as well?

I think there is no need to have the plugin (automatic translation) set in translation projects that use only main version/branch, which is most of them. But I think that fedora (release-docs-home) deserves it. Potentially, sysadmin guide could also be a candidate for. Release notes not so, as it is reworked almost completely each release.

Basically I can imagine that versioned documentation could use automatic translation by default. Exception is (versioned) documentation that changes often and/or significantly between fedora releases.

The downside of this plugin with mode=translated is that this is an unattended translation

I would not be afraid much, provided the documentation (project) is rather stable between the releases. I regard fedora for one of the really stable documentation.

Does the above make sense?

For reference a post from Ask Fedora. But I am not 100% sure it is related.

Does the above make sense?

It does, indeed.

@jibecfed @darknao Do you have an opinion regarding enabling "Automatic translation" plugin for fedora-docs-l10n-fedora regarding the Fedora Linux User Documentation ? (see my considerations in the previous message)

I'm fine with it. We can configure it with translation mode for untranslated strings only, with machine translation using the Weblate Translation Memory and a threshold of 100%

Ok, I installed the add-on in this project with mode=translated and filter=untranslated based on all other components. I see some f40 translated, so it seems to be working.