Internationalization of technical terms and proper nouns
In support of the internationalization work including translate.gitlab.com, we should provide guidance to translators about the handling of technical terms. Crowdin provides a glossary that makes this information available in context.
So far I've identified three groups of terms that we should consider documenting, git terms (branch
, commit
etc), common technical terms (changelog
, readme
), proper nouns (wiki
), marketing terms (GitLab Pages
).
git
terminology
Git terms and defaults should generally NOT be translated, unless being used to explain a git concept. This helps maintain consistency between GitLab and the git client.
List of git terms
- bisect - blame - branch - checkout - cherry pick - clean - clone - commit - diff - fetch - fetch - fork - git - log - master - merge - origin - pull - push - rebase - remote - repository - revert - stash - submodule - tag - upstreamOther terms
- changelog (#38101)
- readme
- license
Nouns
- Issue
- Issue Weight
- Merge Request
Marketing terms and proper nouns
These should not be translated.
- GitLab
- GitLab.com
- Community Edition
- CE
- Enterprise Edition Starter
- EES
- Enterprise Edition Premium
- EEP
- Free Plan
- Bronze Plan
- Silver Plan
- Gold Plan
- GitLab Pages (https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/14509#note_41595060)
- GitLab Geo
- Auto DevOps
- Complete DevOps
- Wiki