Skip to content

Improve plural operand handling #1091

Open
@echeran

Description

@echeran

In case we're not already doing it, we should make sure that when parsing a string representing a number and/or performing PluralRules::select():

  • we parse both compact notation (1.2c3) and scientific notation (1.2e)
  • distinguish the c operand from the e operand, to future-proof when those behave differently
  • make sure we compute plural operands correctly for numbers with exponents (the examples list from the latest spec makes for good test cases)

Metadata

Metadata

Assignees

Labels

C-pluralrulesComponent: Plural rulesS-mediumSize: Less than a week (larger bug fix or enhancement)T-coreType: Required functionality

Type

No type

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions