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

CLDR Ticket #7960(closed: fixed)

Opened 4 years ago

Last modified 4 years ago

Unicode Currency ID, etc.

Reported by: mark Owned by: mark
Component: xxx-spec Data Locale:
Phase: final Review: pedberg
Weeks: Data Xpath:
Xref:

Description

We say things like "ISO 4217 code, plus others in common use" in the spec, but we need to be much more formal about this. That helps us avoid problems such as we had with the currency mapping table, and gives users a strong sense of what to expect. I recommend that we have a formal definition of Unicode Currency ID and similar items. In all cases, we make it clear where these are based on other standards, and how they track them, but we then have a formal way for people to reference what we use, which may be are extensions of the base standards.

Eg.

The /Unicode Currency Identifier/ is used for identifying currencies in software. It is based on 4217, and tracks it closely, but also adds some additional codes for currencies in common use. The values are always 3 ASCII letters, compared case-insensitively. They are listed explicitly in bcp47/currency.xml. For more information, see XXX.

and so on.

This should be done for each of the items in http://www.unicode.org/reports/tr35/#Key_Type_Definitions

Attachments

Change History

comment:1 Changed 4 years ago by emmons

  • Status changed from new to assigned
  • Component changed from unknown to data-supplemental
  • Priority changed from assess to medium
  • Phase changed from dsub to rc
  • Milestone changed from UNSCH to 27
  • Owner changed from anybody to mark

comment:2 Changed 4 years ago by mark

  • Phase changed from rc to final
  • Component changed from data-supplemental to spec

comment:3 Changed 4 years ago by mark

Review note: BTW, when I did a "Cleanup Source" in Eclipse, text changed by other tickets was reformatted. Only the Modifications and the Key/Type definitions (and the date at the top) should have material changes.

So it might be easier to review the HTML with change highlight in those areas.

comment:4 Changed 4 years ago by mark

  • Status changed from assigned to reviewing
  • Review set to pedberg

comment:5 Changed 4 years ago by pedberg

  • Status changed from reviewing to closed
  • Resolution set to fixed
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.