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

CLDR Ticket #9984(accepted)

Opened 2 years ago

Last modified 5 weeks ago

Add readme to data directories, change names.

Reported by: mark Owned by: anybody
Component: to-assess Data Locale:
Phase: rc Review:
Weeks: Data Xpath:


Fix problems in the data directories by making the following changes.

  • Change 'core.zip' to 'common.zip' (or cldr-common-30.0.3.zip to cldr-core-30.0.3.zip), consistently.
  • Add a ReadMe.txt with the following contents:
    This directory contains data files for a cldr release. To find out more information about the release, see http://cldr.unicode.org/index/downloads.
    * The versioned zip files are identical to the corresponding non-versioned files of the same name. For example, in http://unicode.org/Public/cldr/X.Y.Z/, cldr-tools-X.Y.Z.zip is identical to tools.zip.
    * Older releases may use the term 'core' instead of 'common'
    * There are other files in the release that are not packaged in this directory. Those are available in SVN. For details, see http://cldr.unicode.org/index/downloads. 
  • Fix http://cldr.unicode.org/index/downloads
    • add a section that talks about the data directories with the above information.
    • In http://cldr.unicode.org/index/downloads#Repository_Organization, mark which directories are in the data directories, and which are only available via svn. Some other fixes need to be made; for example, the text has: "common — CLDR data corresponding to the release", but common is not all the data corresponding to the release; keyboards contains data corresponding to the release. And "seed" is in the release, but just in SVN, not in the data directory. Probably best to, say, bold the sections that are in http://unicode.org/Public/cldr, and have a sentence that says that the bolded sections are in the data directories while the others are available via SVN.

I would suggest making these changes back to http://www.unicode.org/Public/cldr/30/


In 30.0.3 we innovated by adding versioned files:

[ ] cldr-common-30.0.3.zip 13-Dec-2016 10:50 15M
[ ] cldr-keyboards-30.0.3.zip 13-Dec-2016 10:50 1.3M
[ ] cldr-tools-30.0.3.zip 13-Dec-2016 10:53 29M
[ ] core.zip 13-Dec-2016 10:50 15M
[ ] keyboards.zip 13-Dec-2016 10:50 1.3M
[ ] tools.zip 13-Dec-2016 10:53 29M

But there are a number of problems that this exposes.

  • The 'core' and 'common' mean the same thing here, but confusingly use different names.
  • Also, someone going to the directory could be confused into thinking that the versioned and non-versioned files are different.
  • Longer term problems are also exposed, that it isn't clear that the data is not everything in the release, etc.


Change History

comment:1 Changed 2 years ago by mark

change common to core

comment:2 Changed 2 years ago by mark

  • Owner changed from anybody to mark
  • Priority changed from assess to medium
  • type changed from unknown to site
  • Status changed from new to accepted
  • Milestone changed from UNSCH to 31

Can be post release

comment:3 Changed 2 years ago by mark

  • Phase changed from dsub to final

comment:4 Changed 2 years ago by mark

  • Phase changed from final to dsub
  • Milestone changed from 31 to 32

comment:5 Changed 20 months ago by mark

  • Milestone changed from 32 to 33

comment:6 Changed 14 months ago by mark

  • Phase changed from dsub to spec-beta

comment:7 Changed 13 months ago by mark

  • Phase changed from spec-beta to dsub

comment:8 Changed 13 months ago by emmons

  • Milestone changed from 33 to 34

comment:9 Changed 12 months ago by mark

  • Owner changed from mark to anybody
  • Phase changed from dsub to rc

comment:10 Changed 6 months ago by pedberg

  • Milestone changed from 34 to upcoming

CLDR 34 BRS closing item, move all open 34 → upcoming

comment:11 Changed 6 months ago by mark

  • Milestone changed from upcoming to 35-optional

comment:12 Changed 5 months ago by mark

  • Component changed from unknown to to-assess

comment:13 Changed 5 weeks ago by mark

  • Milestone changed from 35-optional to 36-optional

Add a comment

Modify Ticket

as accepted

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

Note: See TracTickets for help on using tickets.