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

CLDR Ticket #7657(accepted data)

Opened 3 years ago

Last modified 2 years ago

da: Incorrect date and currency format

Reported by: mdunn@… Owned by: fredrik
Component: main Data Locale: da
Phase: dsub Review:
Weeks: Data Xpath:
Xref:

ticket:7814

Description

I recommend to apply the official Danish rules for dates and abbreviations (cf. attached Danish Dates and Currency.docx) and make the following adjustments:

For dates:
If EN is mm/dd/yy, DA should be dd.mm.yy (but with no leading zeros on the day or the month)
If EN is mm/dd/yyyy, DA should be dd.mm.yyyy (again without leading zeros on the day or the month)
DA dd-mm-yy should be dd.mm.yy

For currency:
kr should always have a period at the end: kr.

Sources:
Retskrivningsordbogen (RO) is a Danish orthographic dictionary published by the Danish Language Council to establish the official spelling of the Danish language. According to this, kr. is written with a period.
(http://www.dsn.dk/)

The website sproget.dk is the result of a collaborative effort under the Danish Ministry of Culture between the Danish Language Council (DSN) and the Danish Language and Literature Society (DSL).
(http://sproget.dk/om-sproget-dk)

Attachments

Change History

comment:1 Changed 3 years ago by emmons

  • Owner changed from anybody to fredrik
  • Priority changed from assess to major
  • Status changed from new to assigned
  • Component changed from charts to data
  • Milestone changed from UNSCH to 26rc

comment:2 Changed 3 years ago by fredrik

It seems that the disagreement with current format is that the reporter wants to use periods instead of slashes for separators and eliminate leading zeros on day and month (the format used in the bug descriptions contradicts that, but I suspect that is done in error).

"kr." with period was introduced and won in CLDR 26, so that is a non-issue.

I have made contact with our Danish linguists to get their perspective on the date format.

comment:3 Changed 3 years ago by pedberg

  • Milestone changed from 26rc to 27dsub

comment:4 Changed 3 years ago by markus

  • Phase set to dsub
  • Milestone changed from 27dsub to 27

comment:5 Changed 3 years ago by fredrik

This seems to have fallen between the cracks. Revived the the email thread and will update again.

comment:6 Changed 3 years ago by fredrik

  • Owner changed from fredrik to mark

Apple's Danes report that slashes and periods are used interchangeably without a strong prevalence of one or the other. They say they personally prefer slashes, but have no strong objection towards moving to periods other than to preserve data stability.

They do strongly prefer leading zeros. Omitting the leading zero is typically only done when writing by hand, not computer.

Sending to Mark in case he wants to check Google's sources for an opinion.

comment:7 Changed 3 years ago by mark

  • Owner changed from mark to fredrik

Didn't see this earlier. No objection to making numeric formats be 0 padded (dd instead of d). We should never use yyyy, just y. Otherwise sounds like we should leave the separator as is for now, for stability, unless it looks like there is a sea change.

Giving back to Fredrik

comment:8 Changed 3 years ago by fredrik

  • Data Locale changed from da_DK to da
  • Milestone changed from 27 to 28

Seems we don't have perfect consistency in Danish right now. Formats seem to vary depending on if they're intervals or not. However, this is too late for 27 so pushing to the summer release and will alert vetters to look at this more closely and clean it up.

comment:9 Changed 3 years ago by fredrik

  • Xref set to 7814

comment:10 Changed 3 years ago by markus

  • Type changed from defect to data

comment:11 Changed 3 years ago by srl

  • Status changed from assigned to accepted

comment:12 Changed 2 years ago by fredrik

  • Summary changed from Incorrect date and currency format to da: Incorrect date and currency format

comment:13 Changed 2 years ago by emmons

  • Milestone changed from 28 to 28roll

Moving all outstanding 28 tickets to 28roll. We will discuss disposition of these at the next CLDR TC.

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.