Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Design and implement algorithmic numbering systems (RBNF) #595

Open
sffc opened this issue Apr 1, 2021 · 1 comment
Open

Design and implement algorithmic numbering systems (RBNF) #595

sffc opened this issue Apr 1, 2021 · 1 comment
Labels
A-design Area: Architecture or design A-scope Area: Project scope, feature coverage C-numbers Component: Numbers, units, currencies help wanted Issue needs an assignee S-epic Size: Major project (create smaller child issues) T-core Type: Required functionality

Comments

@sffc
Copy link
Member

sffc commented Apr 1, 2021

Many people around the world use non-decimal numbering systems. CLDR calls these "algorithmic", and ICU implements them in RuleBasedNumberFormat (RBNF). Some use cases include:

  1. Chinese traditional numbering systems, including financial and calendrical
  2. Spellout, like "one", "two hundred", "fifteen thousand and three"
  3. Ordinal, like "1st", "2nd", "10th"

Before implementing RBNF in ICU4X, we should spend some time designing what a good modular API would look like, and how closely to tie it in with decimal formatting.

@sffc sffc added T-core Type: Required functionality A-design Area: Architecture or design A-scope Area: Project scope, feature coverage C-numbers Component: Numbers, units, currencies labels Apr 1, 2021
@sffc sffc added S-epic Size: Major project (create smaller child issues) backlog help wanted Issue needs an assignee labels Apr 19, 2021
@Manishearth
Copy link
Member

This would be implementing the RBNF part of UTS 35, though likely not parsing the CLDR XML format directly.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-design Area: Architecture or design A-scope Area: Project scope, feature coverage C-numbers Component: Numbers, units, currencies help wanted Issue needs an assignee S-epic Size: Major project (create smaller child issues) T-core Type: Required functionality
Projects
None yet
Development

No branches or pull requests

2 participants