yongqli / icu4x

Solving i18n for client-side and resource-constrained environments.

ICU4X

Welcome to the home page for the ICU4X project.

ICU4X provides components enabling wide range of software internationalization. It draws deeply from the experience of ICU4C, ICU4J and ECMA-402 and relies on data from the CLDR project.

The design goals of ICU4X are:

• Small and modular code
• Pluggable locale data
• Availability and ease of use in multiple programming languages
• Written by i18n experts to encourage best practices

Stay informed! Join our public, low-traffic mailing list: [email protected]. Note: After subscribing, check your spam folder for a confirmation.

Documentation

For an introduction to the project, please visit Introduction to ICU4X for Rust tutorial.

For technical information on how to use ICU4X, visit our API docs.

More information about the project can be found in the docs subdirectory.

Quick Start

An example ICU4X powered application in Rust may look like this:

icu = "0.2"
icu_provider_fs = "0.2"

use icu::locid::locale;
use icu::datetime::{DateTimeFormat, mock::datetime::MockDateTime, options::length};
use icu_provider_fs::FsDataProvider;

fn main() {
    let date: MockDateTime = "2020-10-14T13:21:00".parse()
        .expect("Failed to parse a datetime.");

    let provider = FsDataProvider::try_new("/home/{USER}/projects/icu/icu4x-data")
        .expect("Failed to initialize Data Provider.");

    let options = length::Bag {
        time: Some(length::Time::Medium),
        date: Some(length::Date::Long),
        ..Default::default()
    }.into();

    let dtf = DateTimeFormat::try_new(locale!("pl"), &provider, &options)
        .expect("Failed to initialize DateTimeFormat");

    let formatted_date = dtf.format(&date);

    println!("📅: {}", formatted_date);
}

Development

ICU4X is developed by the ICU4X-SC. We are a subcommittee of ICU-TC in the Unicode Consortium focused on providing solutions for client-side internationalization. See unicode.org for more information on our governance.

Please subscribe to this repository to participate in discussions. If you want to contribute, see our contributing.md.

Charter

For the full charter, including answers to frequently asked questions, see charter.md.

ICU4X is a new project whose objective is to solve the needs of clients who wish to provide client-side i18n for their products in resource-constrained environments.

ICU4X, or "ICU for X", will be built from the start with several key design constraints:

1. Small and modular code.
2. Pluggable locale data.
3. Availability and ease of use in multiple programming languages.
4. Written by i18n experts to encourage best practices.

ICU4X will provide an ECMA-402-compatible API surface in the target client-side platforms, including the web platform, iOS, Android, WearOS, WatchOS, Flutter, and Fuchsia, supported in programming languages including Rust, JavaScript, Objective-C, Java, Dart, and C++.

Benchmark dashboards

The performance benchmarks are all run on Ubuntu, and are broken out by component.

• locid
• collections
• fixed_decimal
• plurals
• datetime

The memory benchmarks are run separately on each platform, and examples are individually instrumented.

• macOS
• Ubuntu
• Windows

The binary size benchmarks run on Ubuntu, and are broken out by file type.

• wasm binaries
• gzip'd wasm binaries

The data size benchmark tracks size of provider/testdata/data/testdata.postcard and runs on Linux.

• data size