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

CLDR Ticket #8405(closed: fixed)

Opened 4 years ago

Last modified 21 months ago

4+ international currency symbols not well defined

Reported by: travis Owned by: mark
Component: numbers Data Locale:
Phase: final Review: pedberg
Weeks: Data Xpath:
Xref:

ticket:8359

ticket:8381

ticket:8461

Description (last modified by travis) (diff)

For year fields, e.g yyyy, we define excessive y's to mean zero pad on the left to make that field that many digits. There is no similar definition for 4+ international currency symbols when formatting numbers.

1 currency symbol == symbol ($)
2 currency symbols == ISO code (USD)
3 currency symbols == spelled out form (US dollars)
4 currency symbols == ???
5 currency symbols == ???

For instance implementations could treat 5 currency symbols as 3 + 2, 2 + 3, 1 + 1 + 1 + 2 etc. giving US dollarsUSD, USDUS dollars, $$$USD etc.

Expected behavior: 4+ international currency symbols should be reserved for future use. That way we can extend currency formatting if we choose without it being a breaking change. We should specify that if a client chooses to use a reserved pattern of 4+ international currency symbols, it will be treated literally until such time that it is assigned other behavior. That is 5 international currency symbols in a pattern would format as 5 international currency symbols without any currency localization.

Please see ticket http://bugs.icu-project.org/trac/ticket/11647

Attachments

Change History

comment:1 Changed 4 years ago by travis

  • Xref set to 8359

comment:2 Changed 4 years ago by travis

  • Description modified (diff)

comment:3 Changed 4 years ago by emmons

  • Status changed from new to accepted
  • Component changed from unknown to numbers
  • Priority changed from assess to medium
  • Phase changed from dsub to final
  • Milestone changed from UNSCH to 28
  • Owner changed from anybody to emmons
  • type changed from unknown to spec

comment:4 Changed 4 years ago by pedberg

  • Xref changed from 8359 to 8359 8461

See also cldrbug 8461:

comment:5 Changed 4 years ago by mark

  • Owner changed from emmons to mark

John's going on vacation, so taking.

comment:6 Changed 4 years ago by mark

  • Status changed from accepted to reviewing
  • Review set to travis

comment:7 Changed 4 years ago by mark

http://unicode.org/cldr/trac/ticket/8461 closed as dup, but capturing text here:

In http://unicode.org/reports/tr35/tr35-numbers.html#Contents, make the following change:

OLD

Currency sign, replaced by currency symbol for the currency being formatted. If doubled, replaced by the international currency symbol (U+00A4). If tripled, replaced by the appropriate currency display name for the currency, based on the plural rules in effect for the locale. (For example, "5.00 US Dollars"). Refer to the formatting in for long display names, steps 2 and 4 in Currencies. If present in a pattern, the monetary decimal separator and grouping separators (if available) are used instead of the numeric ones.

NEW

Currency sign, replaced by localized currency symbol for the currency being formatted.

  • ¤ — replaced by the normal, localized symbol, such as "C$".
  • ¤¤ — replaced by the international currency symbol, such as "CAD".
  • ¤¤¤ — replaced by the appropriate currency display name for the currency, based on the plural rules in effect for the locale. (For example, "5.00 US Dollars"). Refer to the formatting in for long display names, steps 2 and 4 in Currencies. If present in a pattern, the monetary decimal separator and grouping separators (if available) are used instead of the numeric ones.
  • ¤¤¤¤¤ — replaced by the narrow currency form, such as "$". The same symbols may be used for multiple currencies. Thus this is be ambiguous, and should only be used where the context is clear.
  • other — reserved for future use.

Also comment: Should the narrow form ¤¤¤¤¤ fallback to the normal mode ¤ when the narrow form isn't available? For example (using English locale), narrow(PLN) = zł, but narrow(CHF) = CHF?

comment:8 Changed 4 years ago by pedberg

  • Xref changed from 8359 8461 to 8359 8381 8461

The latest changes for this also cover the change in cldrbug 8381: so resolving that as a dup of this

comment:9 Changed 4 years ago by pedberg

  • Status changed from reviewing to closed
  • Resolution set to fixed
  • Review changed from travis to pedberg

comment:10 Changed 21 months ago by shane

The spec says that 5 currency symbols, ¤¤¤¤¤, is for narrow. Why not 4 currency symbols, ¤¤¤¤, which has no other meaning? Is this intentional or is it an oversight?

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.