phensley / cldr-engine Goto Github PK

New features
Backwards-compatible
Internal schema breaking changes (applications must load resource packs from the same major.minor version)
CLDR data upgrades which maintain backwards-compatibility

MAJOR

Public API breaking changes
CLDR data upgrades which change break API compatibility (unit deprecation / renaming, etc)

Features

Implementation folows the CLDR specification supporting CLDR version 44.0.0
394 modern locales
Compact resource packs containing all scripts and regions for a given language
Language tag parsing, locale resolution, and distance-based enhanced language matching for improved locale fallback
Fast, compact, and extensible ICU message formatting
Both string and parts formatting for flexible markup styling
Date time, date interval, and relative time formatting
Full IANA and CLDR timezone support covering the full range of IANA timezone untils, automatic handling of deprecated timezone identifiers and aliases
Gregorian, ISO-8601, Japanese, Persian and Buddhist calendars.
Date formatting using flexible skeleton-based pattern matching
Date addition, date subtraction, date differencing and "field of visual difference" calculation
Cardinal and ordinal pluralization rules
Decimal numbers, currencies, units, and unit sequence formatting, with 184 different units
Arbitrary precision decimal math
Display names for languages, scripts, regions, currencies, units, calendar fields, etc
List formatting, measurement system, character order, and line order information
Optional Unit conversion package to convert quantities between CLDR units

Package Naming

Packages with the cldr-* prefix represent pieces of the larger library and are designed to work together. The @phensley/cldr package pulls in the full functionality of the library.

Packages without the cldr-* prefix can be used in an application individually without pulling in the larger core library.

You can use any of the packages independent of the rest of the library:

package	size	dependencies
`@phensley/cldr-utils`
`@phensley/decimal`
`@phensley/language-tag`
`@phensley/locale`		size includes `language-tag` package
`@phensley/locale-matcher`		size includes `locale` and `language-tag` packages
`@phensley/messageformat`		size includes `cldr-utils`, `decimal`, and `plurals` packages
`@phensley/plurals`		size includes `decimal` package
`@phensley/timezone`		size includes `cldr-utils` package
`@phensley/unit-converter`		size includes `cldr-utils` and `decimal` packages

Goals

Support a broad set of CLDR features in the browser "out of the box".
Support all scripts and regions for a language in a single compact resource pack.
Resolve the CLDR data size and dimensionality problems.
- In the case of English: ~49MB of JSON for 106 locales is compressed to a 227KB resource pack (42KB gzip), a factor of approx. 220:1 uncompressed, 1200:1 with gzip compression.
No additional library dependencies required.
No custom extraction of CLDR data or precompilation of formatters required.
Correctness and consistency across browsers, Node.js, and other Javascript ES5 runtime environments.
Provide type-safety, reducing programming errors.
No familiarity with CLDR structure is required for developers to use this library.
High performance.
Arbitrary precision decimal math, to achieve the same accuracy in the browser as on the server.

License

Copyright 2018-present Patrick Hensley

Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at

    http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.

Affiliation

This project is not affiliated with the Unicode Inc. or the Unicode CLDR project.

cldr-engine's People

Contributors

Stargazers

Watchers

Forkers

evasomething tim-stasse

cldr-engine's Issues

Time interval and 'begin-sentence' context

This is more a question than a bug report.
In a time interval, when I use the default 'middle-of-text' context with the fr language, this is what I get:

cldr.Calendars.formatDateInterval(
  start,
  end,
  {
    skeleton: 'yMMMEd',
    context: 'middle-of-text',
  }
)

mar. 1 janv. – mar. 31 déc. 1963

Now, with context set to 'begin-sentence', I get the following:

Mar. 1 janv. – Mar. 31 déc. 1963

I would expect 'begin-sentence' to return something like this:

Mar. 1 janv. – mar. 31 déc. 1963

With only the first part of the interval capitalised, and the second part in lower case.

Is this the intended behaviour of CLDR?

Can this library tell me properties like `groupSeparator` and `decimalSeparator`

I need them to pass to a currency input, so that I can match the input format to the locale. I've had a look but the data format is quite complex, so though I would ask if/how I would go about retrieving this data for a specific locale?

General.getLanguageDisplayName returns nothing for multi-subtag language tags

Hey Patrick,

I stumbled upon this small bug, just thought I would leave this for you here. Testing for v0.25.1 with an English bundle loaded, this statement returns nothing instead of "Simplified Chinese":

cldr.General.getLanguageDisplayName('zh-Hans');

It only works for plain language ids, like 'en' or 'es'. I've included a snippet from the English bundle for reference, note that in most cases, the tag in question includes a region subtag, except in the case of Chinese.

"ar-001": "Modern Standard Arabic",
"de-AT": "Austrian German",
"de-CH": "Swiss High German",
"en-AU": "Australian English",
"en-CA": "Canadian English",
"en-GB": "British English",
"en-US": "American English",
"es-419": "Latin American Spanish",
"es-ES": "European Spanish",
"es-MX": "Mexican Spanish",
"fa-AF": "Dari",
"fr-CA": "Canadian French",
"fr-CH": "Swiss French",
"nds-NL": "Low Saxon",
"nl-BE": "Flemish",
"pt-BR": "Brazilian Portuguese",
"pt-PT": "European Portuguese",
"ro-MD": "Moldavian",
"sr-ME": "Montenegrin",
"sw-CD": "Congo Swahili",
"zh-Hans": "Simplified Chinese",
"zh-Hant": "Traditional Chinese",

(Source: https://github.com/unicode-cldr/cldr-localenames-modern/blob/master/main/en/languages.json)

Example on codesandbox.io

Possible issue location

https://github.com/phensley/cldr-engine/blob/master/packages/cldr-schema/src/code/names.ts#L6

Once again, thanks for all the hard work.

Get time interval with formatDateInterval

I'm trying to get a localised time interval using cldr.Calendars.formatDateInterval. It always returns the date no matter what skeleton I pass as an option. e.g.:

cldr.Calendars.formatDateInterval(
  start,
  end,
  {
    skeleton: 'Hmm',
    ca: 'gregory',
  }
)

Returns something like this with the ja language:

1/1 18:15～12/31 18:45

I'd like to get:

18:15～18:45
// Or even better:
18時15分～18時45分

When I look inside the language pack for Japanese, I see patterns like this one:

H時mm分～H時mm分

So it looks like the information is there, but somehow not surfaced.

I'd like to either have this function to comply more closely to the skeleton or a different function called cldr.Calendars.formatTimeInterval.

CLDR: let's talk

Hi, @phensley — stumbled on this while trying to get another beta of the cldr json v38 data out.

tl;dr (yes, sounds like cldr) is, let's talk! Can you drop me an email? All my contact info is at https://github.com/srl295

Looking at:

I'm working on https://unicode-org.atlassian.net/browse/CLDR-14258 right now.

anyway, i'm working on another drop of the v38 beta CLDR JSON data on NPM. - i'll send an email to cldr-users when ready… It's already checked in to the new monorepo on the branch https://github.com/unicode-org/cldr-json/tree/for-38-beta2

Date/Number parsing

Hi there, I was just wondering if there are any plans to add parsing to the feature stack. In some scenarios it would be nice to parse the date or number against the current user culture.

Regards
Benjamin

phensley / cldr-engine Goto Github PK

cldr-engine's Introduction

cldr-engine

Links

Install

Versioning