Number skeleton precision-increment needs more specification

Description

While implementing a JavaScript parser & formatter for number skeletons, I came across the following open questions related to the precision-increment skeleton token:

  • Does a token like precision-increment/0.05 imply that the output should have exactly two fractional digits? Specifically, with that skeleton should 0.21 be formatted as "0.2" or "0.20"?

  • In what order should precision-increment and scale be applied? For example, with a skeleton like precision-increment/0.1 scale/10, would 0.42 be formatted as "4", "4.0" or "4.2" in an en-US locale? I rather hope that the order of the tokens does not matter here.

  • Can precision-increment be applied together with another precision token? In other words, what would be the effect of a skeleton like precision-increment/0.05 .00? Would that cause a parser error, or would that format a value like 0.09 as "0.09", "0.1", or "0.10"? This is perhaps related to an even more general error, of not specifying what happens when overlapping tokens are included in the same skeleton.

Assignee

Shane Carr

Reporter

Eemeli Aro

Components

Labels

Reviewer

None

Priority

medium

Time Needed

None

Fix versions

Configure