[Translation] GitLab Translator’s Wiki

We should create ‘GitLab Translator’s Wiki’ where we (as GitLab) should place all the rules (general and concreate) translators should follow (btw, I know of this very basic introduction, but it is basic and not sufficient IMO).

You may call it differently (like the ‘GitLab Knowledge Base’) if you wish.

I have talked about this in gitlab-ce#64200.

added Category:Internationalization devopsmanage groupoptimize typefeature labels

Setting "group::measure" based on gitlab-ce3081804.

added 1 deleted label and removed groupoptimize label

added [deprecated] Accepting merge requests label

removed [deprecated] Accepting merge requests label

mentioned in issue #31986 (closed)

mentioned in issue #32498 (closed)

mentioned in issue #32974 (closed)

mentioned in issue #33500 (closed)

mentioned in issue #33958 (closed)

mentioned in issue #34465 (closed)

mentioned in issue #35029 (closed)

mentioned in issue #35482 (closed)

mentioned in issue #35976 (closed)

mentioned in issue #36567 (closed)

mentioned in issue #37182 (closed)

mentioned in issue #37860 (closed)

mentioned in issue #39002 (closed)

mentioned in issue #103403 (closed)

mentioned in issue #121480 (closed)

mentioned in issue #193027 (closed)

mentioned in issue #195099 (closed)

mentioned in issue #196463 (closed)

mentioned in issue #197797 (closed)

mentioned in issue #198979 (closed)

mentioned in issue #207751 (closed)

mentioned in issue #208613 (closed)

mentioned in issue #209697 (closed)

mentioned in issue #211273 (closed)

mentioned in issue #212097 (closed)

mentioned in issue #212790 (closed)

mentioned in issue #212803 (closed)

mentioned in issue #29925 (closed)

mentioned in issue #213478 (closed)

mentioned in issue #214170 (closed)

added to epic &2722

changed milestone to %Awaiting further demand

Hi @tukusejssirs 👋

Are you suggesting a Wiki with general rules (for all languages) or language-specific translation guidelines?

added [deprecated] Accepting merge requests label

Both. I think we should have a single place for all rules, guidelines, things we have agreed upon (etc) concerning translation/l10n. General (language-independent and also general by nature of the rule itself) and specific/detailed rules should be there too.

Reasoning: [new] translators could read tne rules before translation and thus eliminate wrongly translated strings. Reviewers could simplly link a specific rule if a change is required.

It might be also a good idea to list all rules (incl the links to them) that affect a specific string in a note.

added sectiondev label

added groupimport and integrate label and removed 1 deleted label

This issue proposes creating a comprehensive 'GitLab Translator's Wiki' or 'GitLab Knowledge Base' to centralize all translation rules, guidelines, and best practices for GitLab translators, covering both general and language-specific information.

There is currently no plan to do exactly that.

Instead:

1. There are existing docs on translation process: https://docs.gitlab.com/ee/development/i18n/translation.html
2. There are plans to improve the Crowdin glossary and its management:

• Glossary management for GitLab product translat... (gitlab-com/localization/localization-team#278)
• Improve the Crowdin glossary (gitlab-com/localization/localization-team#233)

3. There is ongoing work to provide translators with tools that they can use to enhance their translation process with research and context: Provide context to translators during translati... (gitlab-com/localization&81)
4. There are other initiatives in planning by the Localization team, such as the implementation of a terminology management system, style guides, etc.

All of the above is meant to equip translators with context and language assets, thus help improve consistency, quality, and efficiency of the translation process.

I am closing the issue.

cc @wortschi

closed

assigned to @opysaryuk