39.0.0-BETA2

• published as 39.0.0-BETA2 in npm also.
• Based on release-39-beta2 CLDR data.

Details:

• cldr code: http://github.com/unicode-org/cldr/commit/ae70f97c481e6a91ffa5a6b1167f23bba8e635cd ( maint-39 ) due to CLDR-14639
• cldr data: http://github.com/unicode-org/cldr-staging/commit/c9c485e949e2619bbff393989901815d96e791bb release-39-beta2 from cldr-staging

CLDR JSON 38.1.0

CLDR 38.1 in JSON format.

Downloading

Lots of ways to download this:

• published to npm as @38.1.0 (and also @latest!)
• ZIP files below
• the 38.1.0 git tag in this repo.

the absolute current master CLDR as of this writing

1. gets the licensing wrong for bower
2. doesn’t support -V (so you’ll see cldrVersion 39 instead fo 38

both fixed in unicode-org/cldr#972

• It also will need unicode-org/cldr#983 to not get a MapComparator error, but that PR doesn’t pass CLDR’s unit tests. Will work on that.

• somehow, the exemplarCity for Australia/Currie disappears in zoneNames. Some very recent change in CLDR.

Changes

Also see the CLDR 38.1 release notes.

Summary of JSON changes:
- These items are now arrays instead of strings:
- supplemental/calendarPreferenceData
- supplemental/weekData (now grouped by territory)
- Previously MISSING data now added
- cldr-core/dayPeriods.json: dayPeriodRuleSet-type-selection"
- cldr-core/units.json: unitConstants, unitQuantities
- cldr-core/unitsMetadata.json: unit deprecations

Also:

• new submodule: cldr-segments-full

Also:

• annotations are back!
• full vs modern single zipfiles ( see CLDR-14258 and CLDR-14260 )
• many other fixes.

👉 Also see https://github.com/unicode-org/cldr-json/releases/tag/38.0.0 for some changes that happened in the 38 timeframe.

Colophon

• The PR for this data change was #20
• DATA: cldr-staging unicode-org/cldr-staging@10deb01 (which is release-38-1 of staging, not including chart updates.)
• TOOLS: This was generated from WIP commit unicode-org/cldr@d47f8de … We expect to have a single stable commit that generates this identical JSON in the future. For now, this is the equivalent to:
  • CLDR unicode-org/cldr@4fc4991
  • plus the fix in unicode-org/cldr#972 for license metadata in bower
  • plus the fix in unicode-org/cldr#986 to fix a regression using now-deprecated units
  • plus a forthcoming fix to reinstate Australia/Currie in timeZoneNames

CLDR 38.1, fourth beta

NOTE For details of 38.1 itself, see http://cldr.unicode.org/index/downloads/cldr-38

npm publishing to 38.1.0-BETA4 and retagging as beta

See changelog in 47499d9

• generated from cldr-staging 1acbe10c8af48794cbe9966cb9a6cea92cee6004
  

• generated from cldr tools af9f22440978814cd0724de9cb14e2ffeecf4b48 ( unicode-org/cldr#888 )

Feedback? Consider reviewing the above PR if you are so inclined.

PR for the data change itself: #20

Summary of recent changes:

Summary of changes:
- These items are now arrays instead of strings:
- supplemental/calendarPreferenceData
- supplemental/weekData (now grouped by territory)
- Previously MISSING data now added
- cldr-core/dayPeriods.json: dayPeriodRuleSet-type-selection"
- cldr-core/units.json: unitConstants, unitQuantities
- cldr-core/unitsMetadata.json: unit deprecations

Also:

• new submodule: cldr-segments-full

Also:

• annotations are back!
• full vs modern zipfiles
• many other fixes.

See https://github.com/unicode-org/cldr-json/releases/tag/38.0.0 for some changes that happened in the 38 timeframe.

38.1.0-BETA3

updated packages
and everything uploaded to npm as 38.1.0-BETA3

• new submodule: cldr-segments-full
• reintroduced: cldr-annotations-full and cldr-annotations-modern

Please give pre-release feedback on https://unicode-org.atlassian.net/browse/CLDR-14258

I forgot to mention it in the tag, but this is built from:

• cldr-staging 10deb010d39fcd3c690dac39839811e88dc879b3 ( maint-38-1 almost-final…)
• cldr source 232c58474fc73fa690c093fc9c5ece59ce807eb6 - on my private branch for PR unicode-org/cldr#888

38.1.0 beta

beta, with experimental packaging as in https://unicode-org.atlassian.net/browse/CLDR-14260

CLDR 38.0.0 JSON data

CLDR version 38, in JSON format. See CLDR 38 release notes.

Published to npm as version 38.0.0 and tag latest.

How to use

See the README at https://github.com/unicode-org/cldr-json for general information about cldr-json

What's New

Supplemental (cldr-core)

• grammaticalFeatures.json / grammaticalGenderFeatures.json — Grammatical metadata
• unitPreferenceData.json — Unit Preferences

Misc (cldr-misc-*)

• typographic.json — Translations of Typographic terms

RBNF (cldr-rbnf)

• RBNF data is in a completely new format. The previous format was unusable.

beta 2 of the JSON data

published to npm under the version 38.0.0-BETA2 and the tag beta

For example, cldr-units-full@beta or cldr-units-full@38.0.0-BETA2

You can download the zipfile from here which contains all of the data.

See https://unicode-org.atlassian.net/browse/CLDR-14258 for information about the updated JSON format.

NOTE: this data is created from exactly release 38.0 of CLDR data.

• from cldr repo for tools: f7d6d55ca3073b209d3bf2dd9fcf15d28c259e16
• from cldr-staging data: 7c34ff10a243e46a297329cfb7ec42d2df7dcf15 ( = release-38 )

pre-restructure

prior to CLDR-14258 restructuring

38-test1

draft of 38 data

• Tool code: unicode-org/cldr@d322fc5 ( PR unicode-org/cldr#830 ) - includes https://unicode-org.atlassian.net/browse/CLDR-13730 . Not using CLDR 38 release.
• CLDR Staging: https://github.com/unicode-org/cldr-staging/releases/tag/release-38

37.0.0

CLDR 37 - see http://cldr.unicode.org/index/downloads/cldr-37