Welcome to the landing page for all ~"Category:Internationalization" work. Category direction: https://about.gitlab.com/direction/manage/internationalization/ [](https://translate.gitlab.com/) ## Where we are today As stated on the [category direction](https://about.gitlab.com/direction/manage/internationalization/) page, Internationalization is a community-driven effort maintained by the ~"group::import and integrate". The Import group can currently work **only on critical bugs** and **security fixes** for existing Internationalization features, next to our continuing commitment to: - [Do a regular monthly import of the latest translations](https://gitlab.com/groups/gitlab-org/-/epics/3571). We have started importing the latest translations from Crowdin on a regular monthly cadence in April 2020 and intend to continue this process until it is fully automated and continuous. - Support the translation community. This includes providing active guidance on translation decisions, awarding swag to star contributors and encouraging language communities to increase their translation levels. We **encourage and actively support code contributions from the community**. If you are interested in contributing to the translation and localization features, please consider issues from [this list](https://gitlab.com/gitlab-org/gitlab/-/issues?sort=updated_desc&state=opened&label_name[]=Category:Internationalization&label_name[]=Seeking+community+contributions), which directly support GitLab's internationalization efforts. ## Data #### Browser language settings of GitLab users (January 2023) [An internally viewable chart](https://app.periscopedata.com/app/gitlab/508885/Snowplow-Browser-Summary?widget=15931842&udv=0) shows the percentages of users with specific browser languages (this chart excludes localization to create more general buckets). The table below repeats chart's data, listing top percentages: | Browser language | Percent of users | |------------------------|------------------| | en | 68.02% | | ru | 5.34% | | fr | 5.04% | | es | 4.79% | | pt | 3.23% | | zh | 2.29% | | de | 2.27% | | ja | 1.61% | | pl | 1.04% | | ko | 1.01% | Users can change their preferred language in the UI, irrespective of their browser settings. This is being stored as the `preferred_language`. ~97% of users either have a preferred language of English or it is not set, see [internally viewable chart](https://app.periscopedata.com/app/gitlab/924482/Braza---Shareable-Sandbox?widget=15931259&udv=0). ## Primary target languages Taking into account the browser language preference of GitLab users and which regions are strategically important for GitLab, the following languages have been identified as our primary targets for translations: * Spanish * Chinese (China) * Russian * French * Japanese * Portuguese (Brazil) * German * Korean These strategic languages typically have a large number of native speakers and a strong domestic software development industry (government and academia). While these target languages get additional focus, we will continue to support any language community that wants to translate GitLab. ## Publishing a new language Making a new language choice available for translation and as a choice in GitLab UI is discussed in [this epic](https://gitlab.com/groups/gitlab-org/-/epics/3195). ## Quick action checklist * [ ] Provide better community guidance (what to translate, context for some strings, ...) * [ ] Engage individual translation communities * [ ] Invite language communities to translate * [ ] Promote moderators/proofreaders * [ ] Incentivize engagement * [ ] Prioritize important features * [x] Improve lint to catch security issues * [ ] Auto-reject translations (lint -> CrowdIn) * [ ] Improve translation maintainability * [ ] Developer guidelines - clarify * * [ ] Using multiple plurals * * [ ] No leading/trailing spaces * * [ ] Don't rename %params * * [ ] Specify context for all new strings * * [ ] Distinguish verb from noun in context - i.e. (to) update vs. (the) update