icu4x
icu4x copied to clipboard
Solving i18n for client-side and resource-constrained environments.
One of the formats we should be able to generate ICU4X TimeZone data from is the human-readable file format provided by the [IANA TZDB](https://www.iana.org/time-zones) There are two ways we can...
The TzdbDataProvider from #998 will transform TZDB data into ICU4X data. This data will require the following information for each time zone: 1) IANA TimeZone Identifier 2) DST variant, transition...
We will need a separate DataProvider implementation to package data from the [IANA time-zone database](https://www.iana.org/time-zones). This should live in a separate crate for now with the other data provider implementations.
Tracks progress on issues related to TzdbDataProvider for * #887 Time Zones information will need to come from two sources. The first is from CLDR JSON, so the `CldrJsonDataProvider` will...
We still need to implement the `vv` pattern for TimeZoneFormat, which his the long time zone name. This is the canonical IANA time zone identifier. Depends on: * #992 (TzdbDataProvider)
We still need to implement the `v` pattern for TimeZoneFormat, which his the short time zone name. This is the BCP-47 identifier. Depends on: * #606
# TimeZones 1.0 This aims to be a comprehensive tracking issue for all tasks left in order to consider time zones feature-complete in ICU4X 1.0. If any new issues come...
Tracks progress on issues related to TimeZoneFormat for * #887 - [ ] TimeZoneFormat - #418 - #622 - #1232 - #983 - #984 - #985 - #986 - #987...
The normalizers aren't currently exposed to C++ via Diplomat. They should be. Only the `ComposingNormalizer` and `DecomposingNormalizer` objects should have C++ counterparts. `Composition` and `Decomposition` are Rust iterators, which are...
Currently, the collator isn't exposed to C++ via Diplomat. It should be. Apart from the constructor, the `Collator` object has three public methods in Rust: * `compare()` (takes guaranteed-valid UTF-8)...