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

CLDR Ticket #5672(accepted data)

Opened 4 years ago

Last modified 22 months ago

Make short formats use of yy & y consistent

Reported by: mark Owned by: mark
Component: main Data Locale:
Phase: dsub Review:
Weeks: Data Xpath:
Xref:

Description (last modified by mark) (diff)

I was also looking at the use of y vs yy in short formats.

https://docs.google.com/spreadsheet/ccc?key=0AqRLrRqNEKv-dE5QYk4xQ3NUTlRZbnRpcHZjeGw0M2c#gid=4

I'm convinced that the choice is essentially random; that translators sometimes picked the yy and sometimes y.

To help settle the issue, I'm suggesting is that we query translators by generating the form with 4 digit year and the form with 2 digit year, and ask them *for each of the two* whether it is acceptable. We can then use that information to make our current information more consistent.

Note:

In some cases, the same locale uses yy sometimes and y sometimes:

yy bs_Cyrl.xml generic d.M.yy. GGGGG
yy bs_Cyrl.xml gregorian d.M.yy.
yy bs_Cyrl.xml japanese M/d/yy G
y bs_Cyrl.xml islamic dd.MM.y. G

yy bs.xml generic dd.MM.yy. GGGGG
yy bs.xml gregorian dd.MM.yy.
y bs.xml islamic dd.MM.y. G

In some cases, the locales are consistent, but vary between the regions for the same language

y en_ZA.xml generic GGGGG y/MM/dd
y en_ZA.xml gregorian y/MM/dd
y en_ZW.xml generic d/M/y GGGGG
y en_ZW.xml gregorian d/M/y

yy en.xml buddhist M/d/yy GGGGG
yy en.xml chinese M/d/yy
yy en.xml generic M/d/yy GGGGG
yy en.xml gregorian M/d/yy
yy en.xml islamic M/d/yy G
yy en.xml japanese M/d/yy GGGGG
yy en.xml roc M/d/yy GGGGG
yy eo.xml generic GGGGG yy-MM-dd
yy eo.xml gregorian yy-MM-dd

Attachments

Change History

comment:1 Changed 4 years ago by mark

  • Description modified (diff)
  • Summary changed from Consider changing short formats with yy to y. to Consider how to make short formats more consisten with yy & y

comment:2 Changed 4 years ago by mark

  • Summary changed from Consider how to make short formats more consisten with yy & y to Consider how to make short formats more consistent with yy & y

comment:3 Changed 4 years ago by emmons

  • Status changed from new to assigned
  • Component changed from unknown to data
  • Priority changed from assess to major
  • Milestone changed from UNSCH to 24dsub
  • Owner changed from anybody to mark
  • Type changed from unknown to task

comment:4 Changed 4 years ago by pedberg

  • Cc pedberg added

comment:5 Changed 4 years ago by mark

  • Milestone changed from 24dsub to 24dsub2

comment:6 Changed 4 years ago by mark

  • Milestone changed from 24dsub2 to 24rc

This is done most easily after data is back in ST.

comment:7 Changed 4 years ago by mark

  • Milestone changed from 24rc to 25dsub

comment:8 Changed 4 years ago by emmons

  • Milestone changed from 25dsub to 25rc

Moving all 25dsub and 25design tickets to 25rc. If you plan to complete items in the 25M1 time frame, please move those tickets to 25M1.

comment:9 Changed 3 years ago by mark

  • Milestone changed from 25rc to 26dsub

comment:10 Changed 3 years ago by mark

  • Summary changed from Consider how to make short formats more consistent with yy & y to Make short formats use of yy & y consistent

clarify title

comment:11 Changed 3 years ago by mark

  • Milestone changed from 26dsub to 27

comment:12 Changed 3 years ago by markus

  • Phase set to final

comment:13 Changed 2 years ago by mark

  • Phase changed from final to dsub
  • Milestone changed from 27 to 28

comment:14 Changed 2 years ago by markus

  • Type changed from task to data

comment:15 Changed 2 years ago by srl

  • Status changed from assigned to accepted

comment:16 Changed 2 years ago by mark

  • Milestone changed from 28 to 29

comment:17 Changed 22 months ago by emmons

  • Milestone changed from 29 to upcoming

Automatic move of all 29 -> upcoming

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.