[Summary] Translation system overhaul

[denyskon]

Cleanup translations

• fix issues in translation file #27699
• Cleanup outdated translation strings ([Summary] Translation system overhaul #27700 (comment))
• Dedupe translations #24488
• Removal/Sanitization of HTML from translations #24402

General overhaul

• Use Crowdin action for translation sync #30054
• [Proposal] Use ICU message for i18n & l10n #23863
• Convert locale files to other format due to INI limitations & limited support
• Switch translation platform from Crowdin to Weblate

Docs translation

• Remove non-english docs? #27499
• Remove outdated docs from some languages #27530
• Filter translation documentations by the completeness like UI translation did #24715
• Outdated detectable documentation translation #23316
• Translate all doc files with Crowdin #17081
• Switch to Weblate for translations #20309

[wxiaoguang]

Share some of my thoughts.

Many translations in non-English locale are out-dated or event incorrect, because they didn't get updates when the English messages change.

To make the translations clear, the first step is to git blame every key's change, remove all outdated keys from non-English locales, sync to Crowdin.

[silverwind]

Many translations in non-English locale are out-dated or event incorrect, because they didn't get updates when the English messages change.

We need to invalidate all affected tokens in all languages when english changes, it's the only sane config. It's doubly problematic if the % tokens in the message change, which will break rendering.

[lunny]

Moved this out of 1.22 because a summary issue may cross multiple milestones.

[silverwind]

I think a good first step is when someone with access to crowdin admin panel would take a look at integrating https://github.com/crowdin/github-action, replacing the current ini workflow. Maybe a small script could be written that outputs the ini format to ease the transition.

It would enable contributors to configure crowdin in-repo and likely gain a deeper understanding of the process in turn.

@go-gitea/technical-oversight-committee can anyone with crowdin admin get this started?

[denyskon]

After fighting with the mess in our current translation files again and again, I think these are the steps we need to do:

• 1. Cleanup translation strings massively, reduce amount of translations, get rid of deep nesting.
• 2. Invalidate all translations whose source strings are newer.
• 3. Convert to a better file format, e. g. JSON or YML
• 4. Move translations over to Weblate

We could also do 3. independently, but I don't have an overview of how the files are parsed currently

[silverwind]

One step I would like to do is to flatten the ini to make the keys greppable, e.g. turning

[foo]
bar.baz = qux

into

foo.bar.baz = qux

This can be easily done with a script and should be compatible with all the code. Question is just whether it might break anything regarding the crowdin sync.