#icu #unicode #locale #i18n

icu_locid

API for managing Unicode Language and Locale Identifiers

2 unstable releases

0.2.0 Apr 29, 2021
0.1.0 Oct 15, 2020

#96 in Internationalization (i18n)

44 downloads per month
Used in 14 crates (13 directly)

Custom license

135KB
2K SLoC

icu_locid crates.io

icu_locid is one of the ICU4X components.

This API provides necessary functionality for parsing, manipulating, and serializing Unicode Language and Locale Identifiers.

The crate provides algorithms for parsing a string into a well-formed language or locale identifier as defined by UTS #35: Unicode LDML 3. Unicode Language and Locale Identifiers.

[Locale] is the most common structure to use for storing information about a language, script, region, variants and extensions. In almost all cases, this struct should be used as the base unit for all locale management operations.

[LanguageIdentifier] is a strict subset of [Locale] which can be useful in a narrow range of cases where Unicode Extensions are not relevant.

If in doubt, use [Locale].

Examples

use icu::locid::Locale;
use icu::locid::subtags::{Language, Region};

let mut loc: Locale = "en-US".parse()
    .expect("Parsing failed.");

let lang: Language = "en".parse()
    .expect("Parsing failed.");
let region: Region = "US".parse()
    .expect("Parsing failed.");

assert_eq!(loc.id.language, lang);
assert_eq!(loc.id.script, None);
assert_eq!(loc.id.region, Some(region));
assert_eq!(loc.id.variants.len(), 0);

let region: Region = "GB".parse().expect("Parsing failed.");
loc.id.region = Some(region);

assert_eq!(loc.to_string(), "en-GB");

For more details, see [Locale] and [LanguageIdentifier].

More Information

For more information on development, authorship, contributing etc. please visit ICU4X home page.

Dependencies

~130KB