The Forgejo translations being trapped in a proprietary service would be a blocker in the event of a hard fork. Late 2022 the strategy for localization was to:
- have a script to patch the existing translations where relevant
- add new strings and resolve conflicts weekly (those are not translated at all)
It worked fine until now, the overhead and problems were close to non-existent. Nobody knew Forgejo and establishing a translation team would have been difficult then but things are different now. There are significantly more people aware of what Forgejo is and willing to help. @Werenter recently started to work on it and got inspiration from @delvh previous work.
TODO:
- create a translation team
- propose a localization team forgejo/governance#61
- create a translation https://matrix.to/#/#forgejo-localization:matrix.org
- add the chatroom to the Forgejo space
- agreement finalized for the localization team forgejo/governance#61
- draft of the documentation of the localization team forgejo/governance#62
- document the localization team forgejo/governance#62
- recruit translators to be reviewers vetting translations
- 21 January 2024 call for participation in the development chatroom
- update the website with a link encouraging invovlement
- initial translation team candidates
- Arabic @oatbiscuits
- Dutch @Gusted
- French @dachary
- Russian @0eoc @Werenter
- Hungarian @algernon
- Greek @n0toose
- German @fnetX
- Ukranian @nykula
- document the l10n workflow (see the PR)
- make Forgejo translation files authoritative (see the pull request)
- modify build/merge-forgejo-locales.go to produce a minimal diff
- collect all changes to options/locale/locale_en-US.ini from the feature branches
- cherry pick changes from https://codeberg.org/forgejo/forgejo-translation / https://translate.codeberg.org/projects/forgejo/forgejo-test/
- add
[common]to the beginning of all files. It will be treated as no section and is a requirement for weblate which would otherwise be confused by the absence of section (see also the content duplication bug) - add support for
[common]in addition to[DEFAULT]in Forgejodiff --git a/modules/translation/i18n/localestore.go b/modules/translation/i18n/localestore.go index f5a951a79f..5fc992794e 100644 --- a/modules/translation/i18n/localestore.go +++ b/modules/translation/i18n/localestore.go @@ -54,7 +54,7 @@ func (store *localeStore) AddLocaleByIni(langName, langDesc string, source, more for _, section := range iniFile.Sections() { for _, key := range section.Keys() { var trKey string - if section.Name() == "" || section.Name() == "DEFAULT" { + if section.Name() == "" || section.Name() == "DEFAULT" || section.Name() == "common" { trKey = key.Name() } else { trKey = section.Name() + "." + key.Name() - commit to https://codeberg.org/forgejo/forgejo/src/branch/forgejo-development
- 28 January cleanup
- resolve conflict in
[GITEA] notifies admins on new user registration - remove the forgejo-i18n branch
- merge
frogejo-developmentintoforgejo
- resolve conflict in
- reconfigure https://translate.codeberg.org/settings/forgejo/forgejo/#vcs to use https://codeberg.org/forgejo/forgejo and the forgejo branch
- reset https://translate.codeberg.org/projects/forgejo/forgejo/#repository
image - (hard fork only) run build/crowdin-to-weblate.sh when cherry-picking
- create a forgejo weblate project
- https://translate.codeberg.org/projects/forgejo/
- to enforce the desired workflow the "Enable reviews" button must be set in https://translate.codeberg.org/settings/forgejo/#workflow
- Add a banner so people do not start translating during the transition phase
image - select "Gitea via pull request" strategy, which relies on weblate being configured server side to open pull requests
- create a localization group
image - invite localization team members to the "localization" group
- approve all existing strings, thus preventing them from being modified by random users.
image
- adding weblate translations to Forgejo is done manually by a member of the team merging the weblate pull request
image
Related issues / PRs / branches
The Forgejo translations being trapped in a proprietary service would be a [blocker in the event of a hard fork](https://codeberg.org/forgejo/governance/issues/58). Late 2022 the [strategy for localization](https://codeberg.org/forgejo/discussions/issues/4) was to:
* have a script to patch the existing translations where relevant
* add new strings and resolve conflicts weekly (those are not translated at all)
It worked fine until now, the overhead and problems were close to non-existent. Nobody knew Forgejo and establishing a translation team would have been difficult then but things are different now. There are significantly more people aware of what Forgejo is and willing to help. @Werenter recently [started to work on it](https://codeberg.org/forgejo/forgejo/pulls/2044) and got inspiration from @delvh previous work.
TODO:
- [x] create a translation team
- [x] propose a localization team https://codeberg.org/forgejo/governance/issues/61
- [x] create a translation https://matrix.to/#/#forgejo-localization:matrix.org
- [x] add the chatroom to the Forgejo space
- [x] agreement finalized for the localization team https://codeberg.org/forgejo/governance/issues/61
- [x] draft of the documentation of the localization team https://codeberg.org/forgejo/governance/pulls/62
- [x] document the localization team https://codeberg.org/forgejo/governance/pulls/62
- [x] recruit translators to be reviewers vetting translations
- [x] 21 January 2024 [call for participation in the development chatroom](https://matrix.to/#/!zpNKWqkiEOyljSMQDK:matrix.org/$J5eGFvwazdBJ5GeWxrAy8CB7DRNUY45qwT_yxHHu5Fg?via=schinas.net&via=matrix.org&via=aria-net.org)
- [x] update the website with [a link encouraging invovlement](https://codeberg.org/forgejo/website/pulls/407)
- [x] initial translation team candidates
- Arabic @oatbiscuits
- Dutch @Gusted
- French @dachary
- Russian @0eoc @Werenter
- Hungarian @algernon
- Greek @n0toose
- German @fnetX
- Ukranian @nykula
- [x] [document the l10n workflow](https://forgejo.org/docs/v1.21/developer/localization/) (see [the PR](https://codeberg.org/forgejo/docs/pulls/381))
- [x] make Forgejo translation files authoritative ([see the pull request](https://codeberg.org/forgejo/forgejo/pulls/2197))
- [x] modify build/merge-forgejo-locales.go to produce a minimal diff
- [x] collect all changes to options/locale/locale_en-US.ini from the feature branches
- [x] cherry pick changes from https://codeberg.org/forgejo/forgejo-translation / https://translate.codeberg.org/projects/forgejo/forgejo-test/
- [x] add `[common]` to the beginning of all files. It will be treated as no section and is a requirement for weblate which would otherwise be confused by the absence of section (see also the [content duplication bug]( https://github.com/WeblateOrg/weblate/issues/10831))
- [x] add support for `[common]` in addition to `[DEFAULT]` in Forgejo
```diff
diff --git a/modules/translation/i18n/localestore.go b/modules/translation/i18n/localestore.go
index f5a951a79f..5fc992794e 100644
--- a/modules/translation/i18n/localestore.go
+++ b/modules/translation/i18n/localestore.go
@@ -54,7 +54,7 @@ func (store *localeStore) AddLocaleByIni(langName, langDesc string, source, more
for _, section := range iniFile.Sections() {
for _, key := range section.Keys() {
var trKey string
- if section.Name() == "" || section.Name() == "DEFAULT" {
+ if section.Name() == "" || section.Name() == "DEFAULT" || section.Name() == "common" {
trKey = key.Name()
} else {
trKey = section.Name() + "." + key.Name()
```
- [x] [commit to https://codeberg.org/forgejo/forgejo/src/branch/forgejo-development](https://codeberg.org/forgejo/forgejo/pulls/2197)
- [x] 28 January cleanup
- [x] resolve conflict in `[GITEA] notifies admins on new user registration`
- [x]remove the forgejo-i18n branch
- [x] merge`frogejo-development` into `forgejo`
- [x] reconfigure https://translate.codeberg.org/settings/forgejo/forgejo/#vcs to use https://codeberg.org/forgejo/forgejo and the forgejo branch
- [x] reset https://translate.codeberg.org/projects/forgejo/forgejo/#repository
- (hard fork only) run build/crowdin-to-weblate.sh when cherry-picking
- [x] create a forgejo weblate project
- [x] https://translate.codeberg.org/projects/forgejo/
- [x] to enforce the [desired workflow](https://docs.weblate.org/en/latest/workflows.html#dedicated-reviewers) the "Enable reviews" button must be set in https://translate.codeberg.org/settings/forgejo/#workflow
- [x] Add a banner so people do not start translating during the transition phase
- [x] select "Gitea via pull request" strategy, which relies on weblate being configured server side to [open pull requests](https://docs.weblate.org/en/weblate-5.3.1/vcs.html#vcs-gitea)
- [x] create a localization group
- [x] invite localization team members to the "localization" group
- [x] [approve all existing strings](https://translate.codeberg.org/projects/forgejo/forgejo/#bulk-edit), thus preventing them from being modified by random users.
- [x] adding weblate translations to Forgejo is done manually by a member of the team merging the weblate pull request
## Related issues / PRs / branches
* https://codeberg.org/forgejo/forgejo/src/branch/forgejo-i18n
* https://codeberg.org/forgejo/forgejo/issues/8
* https://codeberg.org/forgejo/discussions/issues/4
* https://codeberg.org/forgejo/meta/issues/72
* https://codeberg.org/forgejo/forgejo/issues/388
* https://codeberg.org/Werenter/forgejo-translation/issues/2
* https://codeberg.org/forgejo/forgejo/pulls/2044