[Unicode]   Common Locale Data Repository : Bug Tracking Home | Site Map | Search
 
Modify

CLDR Ticket #9997(closed spec: fixed)

Opened 7 months ago

Last modified 5 months ago

Locales 'it' and 'gl' should add grouping separators on Compact Decimal Format below 1M

Reported by: sffc@… Owned by: mark
Component: numbers Data Locale:
Phase: spec-beta Review: shane
Weeks: Data Xpath:
Xref:

Description

The decimal formats for these locales on compact decimal format numbers less than 1M are currently "0". This means that a number like 123456 produces the output "120000", when "120.000" (with a grouping separator) might be more appropriate. I see two choices to solve this problem:

  1. Add the grouping separator to the compact decimal format patterns for 5 digits and 6 digits, like "00,000" and "000,000".
  2. Change the CLDR spec to say specifically that if the pattern is "0", then the implementation should fall back to the default decimal pattern for that locale.

Partially related: #9747, #9893

GoogleIssue:34187535

Attachments

Change History

comment:1 Changed 7 months ago by emmons

  • Status changed from new to accepted
  • Priority changed from assess to major
  • Phase changed from dsub to rc
  • Milestone changed from UNSCH to 31
  • Owner changed from anybody to googler
  • Type changed from unknown to data

For Shawn when an account is created.

comment:2 Changed 7 months ago by mark

  • Owner changed from googler to mark

comment:3 Changed 7 months ago by mark

  • Phase changed from rc to spec-beta
  • Type changed from data to spec

The value for these languages is "0", so the decimal format for the calling code should be the normal format. Changing this to a spec bug, and filed ICU ticket http://bugs.icu-project.org/trac/ticket/12975

comment:4 Changed 6 months ago by mark

  • Cc pedberg added
  • Status changed from accepted to reviewing
  • Review set to shane

comment:6 Changed 6 months ago by pedberg

  • Component changed from unknown to numbers

comment:7 Changed 6 months ago by shane

  • Status changed from reviewing to closed
  • Resolution set to fixed

LGTM. Very precise as to what the behavior should be, including examples.

comment:8 Changed 6 months ago by shane

  • Status changed from closed to reviewfeedback

One issue I just noticed: when falling back to <currencyFormat type="standard">, how is the number of decimal places resolved? The example in the draft revision has the currency pattern #,##0.00 ¤ but the formatted output is 990 $.

With currencies in particular, there are three different ways that rounding could potentially be specified:

  1. Via tha pattern.
  2. Via the currency rounding rules (aka CurrencyUsage).
  3. Via significant digit rules.

How should the CompactDecimal fallback resolve currency rounding?

Last edited 6 months ago by shane (previous) (diff)

comment:9 Changed 5 months ago by mark

  • Status changed from reviewfeedback to reviewing
  • Resolution fixed deleted

comment:10 Changed 5 months ago by pedberg

(Mark made another edit to the spec)

comment:11 Changed 5 months ago by shane

  • Status changed from reviewing to closed
  • Resolution set to fixed

The revisions look good.

View

Add a comment

Modify Ticket

Action
as closed
Next status will be 'new'
Next status will be 'closed'
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.