Breaking changes to data file names

[John Emmons]

It's a permanent change. See http://unicode.org/cldr/trac/ticket/8031 for 
the rationale.  Also the change in name from "core" to "common" was done 
by agreement of the CLDR TC yesterday, in order to avoid confusion with 
the cldr-core package being done for the JSON.


Regards,

John C. Emmons
Globalization Architect & Unicode CLDR TC Chairman
IBM Software Group
Internet: emmo at us.ibm.com




From:   "Doug Ewell" <doug at ewellic.org>
To:     cldr-users at unicode.org
Date:   03/19/2015 10:57 AM
Subject:        Breaking changes to data file names
Sent by:        "CLDR-Users" <cldr-users-bounces at unicode.org>



The data files at http://www.unicode.org/Public/cldr/27/ are named:

cldr-common-27.0.zip
cldr-keyboards-27.0.zip
cldr-tools-27.0.zip

Is this a permanent change in the naming scheme, or a development
artifact that leaked out by accident?

If it's permanent, then it breaks the statements in RFCs 6067 (sections
2.1 and 2.2) and 6497 (sections 2.4 and 2.9) that BCP 47 extension data
is located in core.zip. At least the registration records in
language-tag-extensions-registry, and probably the RFCs themselves, will
have to be updated promptly.

--
Doug Ewell | http://ewellic.org | Thornton, CO ����


_______________________________________________
CLDR-Users mailing list
CLDR-Users at unicode.org
http://unicode.org/mailman/listinfo/cldr-users


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://unicode.org/pipermail/cldr-users/attachments/20150319/3cdfdcce/attachment-0001.html>