language code for translations
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 3.6k
- Forks
- 832
- Avg merge
- 7h 55m
- Merged PRs (30d)
- 4
Description
We should pick, document and implement, what is our policy for language codes for translations - like in file names, folder names etc.
Option 1 - use correct 2 letter language codes based on ISO-639-1:
https://en.wikipedia.org/wiki/List_of_ISO_639-1_codes
Option 2 - we can be more precise with language (locale) code, like instead of "en" we should use "en-gb" or "en-us". Then based on that it's possible to make more precise language corrections in documents (and use correct speller). The same may apply for Portuguese (pt-pt, pt-br), Spanish (es-es, es-*), Chinese (zh-cn, zh-*), Arabic (ar-*) etc.
In other words - use "Language-Region" from RFC5646 (https://datatracker.ietf.org/doc/html/rfc5646).
There are some other combinations available as well, so we need to pick one and use only this one.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Review the translation file and folder names in the 4.0 tree, along with the raw .md source files and the linked ISO-639-1 and RFC5646 references. Decide and document one language-code policy, then apply it consistently to the relevant names and derived translation outputs; done means the convention is explicit and consistent.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation, internationalization, localization
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100