internationalization / localization
- Dominant language
- C#
- Stars
- 11.5k
- Forks
- 960
- PR merge metrics
- No merged PRs in 30d
Description
It's probably time to start the conversation on localization of choco itself.
## Proposal
* All messages that are info and above should be localized.
* Errors first as they present the most
* Debug / Trace messages stay in English
* Help text should be localized
### Open Questions:
* [ ] Capture detailed log in English?
* [ ] Capture summary log in Locale?
* [ ] Switch to explicitly force English output?
* [ ] Do we keep config / feature names in English for simplicity?
* [ ] Should we set documentation in the config file in language of the user? What do we do if there are multiple users who might log in?
* [ ] do we allow commands to run based on the language? e.g. `choco search` but search is in locale of the user.
Contributor guide
Research direction
The issue names no files, tests, or entry points. Begin by reviewing the localization proposal and resolving the listed open questions about logs, English overrides, configuration names, documentation, and localized commands. Done would require an agreed scope for localizing informational and error messages plus help text.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- cli, localization
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100