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

CLDR Ticket #4358(accepted)

Opened 7 years ago

Last modified 4 months ago

CLDR tools generates bad currency dates

Reported by: dougfelt@… Owned by: anybody
Component: to-assess Data Locale:
Phase: Review:
Weeks: 0.1 Data Xpath:
Xref:

Description

cldr/tools/java/org/unicode/cldr/icu/SupplementalDataParser.java has a bug. When parsing the CLDR dates for the currency 'from' and 'to' fields, 'long getMilliseconds(String)' uses "yyyy-mm-dd" instead of "yyyy-MM-dd", treating the month field as minutes. So, for example, instead of the DEM currency starting on 1948-06-20, it starts at 1948-01-20 00:06.

This data gets generated as an array of decimal integer values in the source/data/curr/supplementalData.txt file in icu, along with the original string as a comment, so it is not obvious from inspection that the values are wrong-- the comment reflects the original string data from CLDR and not the value that the integers would resolve to.

Attachments

Change History

comment:1 Changed 7 years ago by mark

  • Owner changed from somebody to dougfelt
  • Priority changed from assess to major
  • Status changed from new to assigned
  • Milestone changed from UNSCH to 22

comment:2 Changed 7 years ago by mark

  • Weeks set to 0.1

comment:3 Changed 7 years ago by emmons

  • Milestone changed from 22 to future

comment:4 Changed 5 years ago by emmons

  • Milestone changed from future to UNSCH

Merging future and UNSCH

comment:5 Changed 4 years ago by markus

  • type changed from defect to tools
  • Component changed from tools to unknown

comment:6 Changed 4 years ago by srl

  • Status changed from assigned to accepted

comment:7 Changed 4 years ago by mark

  • Owner changed from dougfelt to googler

comment:8 Changed 4 months ago by mark

  • Owner changed from googler to anybody

comment:9 Changed 4 months ago by mark

  • Component changed from unknown to to-assess
View

Add a comment

Modify Ticket

Action
as accepted
Author


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

 
Note: See TracTickets for help on using tickets.