icu4x
icu4x copied to clipboard
unicode-org
Solving i18n for client-side and resource-constrained environments.
How expressive should UnicodeSet parse errors be? Does it suffice if we show which character at which position was the issue, or should we give precise information also about what...
ICU4C has exhaustive tests. Rust has an equivalent called "ignored" tests, which use the `#[ignore]` annotation. We should consider running these tests on main CI. It would also be nice...
The tests covering gb2312 and big5han were disabled. Upon re-enabling them, they are failing, even after moving the tests into datagen where they should have access to those collation tables....
For ECMA-402 compat, ICU4X should provide support for the `notation: "scientific"` in ECMA-402.
ECMA-402 requires various objects to be able to expose the resolved options. Common across different types is the resolved locale. For ECMA-402 compat, we should make various ICU4X objects call...
In relation to #2683. The current fallback mechanism is quite costly in binary size and data payload to support. In order to enable customers to use ICU4X without it, we...
It reduces dependencies and compilation time.
See #2310 In https://github.com/unicode-org/icu4x/issues/5124 we're trying to slim down ICU4X's deps. A lot of our crates don't need the full power of the ule/varule macros, and it would be nice...
Hi! I tried to run the benchmarks for the library with `RUST_BACKTRACE=full cargo bench --workspace --all-features -p icu_collections --bench iai_cpt` but got the following error: ``` RUST_BACKTRACE=full cargo bench --workspace...
It appears that Temporal CalendarDateYear / LDML extended year isn't exposed. For Temporal compat, it should be exposed. It could potentially be a new field on `FormattableYear`.
Metadata
Owner
Metadata
Solving i18n for client-side and resource-constrained environments.