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