Need to properly deal with plural rules in `i18n.t()`
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- JavaScript
- Stars
- 1.1k
- Forks
- 160
- PR merge metrics
- No merged PRs in 30d
Description
Looks like Intl.PluralRules() might help, or migrating to a proper I18N framework. I didn't find a lightweight one, but maybe by the pure nature they need to be heavy?
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
Start by locating the i18n.t() implementation and its existing translation callers, then compare current plural handling with Intl.PluralRules(). Define the supported plural behavior and a testable completion criterion before choosing between that API and a framework; the issue names no files or tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- internationalization
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100