1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284
// This file is part of ICU4X. For terms of use, please see the file // called LICENSE at the top level of the ICU4X source tree // (online at: https://github.com/unicode-org/icu4x/blob/master/LICENSE ). //! `icu` is the main meta-package of the `ICU4X` project. //! //! It provides a comperhensive selection of Unicode Internationalization Components //! in their canonical configurations intended to enable software //! internationalization capabilities. //! //! The package is provided for convenience and users are encouraged //! to fine-tune components with the features they need. //! //! The package does not bring any unique functionality. Users //! can achieve the exact same by manually including the dependent //! components with pre-selected features. //! //! # Data Management //! //! Most of Unicode functionality relies on data which has to be provided //! to the APIs. //! //! `ICU4X` project uses a concept of [`DataProvider`] - a service used to //! handle data management. //! //! There can be many different heuristics for handling data management and //! this meta-package does not supply any default `DataProvider`. //! //! When using `ICU4X` users are expected to decide which provider they want to use //! and instrument it to point at the correct location where the data files are stored. //! //! In the following examples an [`icu_testdata`] package is used which wraps //! an [`FsDataProvider`] with locally available subset of data. //! //! # Examples //! //! ``` //! use icu::locid::macros::langid; //! use icu::datetime::{DateTimeFormat, date::MockDateTime, options::style}; //! //! let provider = icu_testdata::get_provider(); //! //! let lid = langid!("en"); //! //! let options = style::Bag { //! date: Some(style::Date::Long), //! time: Some(style::Time::Medium), //! ..Default::default() //! }.into(); //! //! let dtf = DateTimeFormat::try_new(lid, &provider, &options) //! .expect("Failed to create DateTimeFormat instance."); //! //! let date: MockDateTime = "2020-09-12T12:35:00".parse() //! .expect("Failed to parse date."); //! //! let formatted_date = dtf.format(&date); //! assert_eq!(formatted_date.to_string(), "September 12, 2020 at 12:35:00 PM"); //! ``` //! //! [`icu_testdata`]: ../icu_testdata/index.html //! [`DataProvider`]: ../icu_provider/prelude/trait.DataProvider.html //! [`FsDataProvider`]: ../icu_provider_fs/struct.FsDataProvider.html pub mod datetime { //! Date and Time operations //! //! This API provides necessary functionality for formatting date and time to user readable textual representation. //! //! [`DateTimeFormat`] is the main structure of the component. It accepts a set of arguments which //! allow it to collect necessary data from the [`DataProvider`], and once instantiated, can be //! used to quickly format any date and time provided. //! //! # Examples //! //! ``` //! use icu::locid::macros::langid; //! use icu::datetime::{DateTimeFormat, date::MockDateTime, options::style}; //! //! let provider = icu_testdata::get_provider(); //! //! let lid = langid!("en"); //! //! let options = style::Bag { //! date: Some(style::Date::Medium), //! time: Some(style::Time::Short), //! ..Default::default() //! }.into(); //! //! let dtf = DateTimeFormat::try_new(lid, &provider, &options) //! .expect("Failed to create DateTimeFormat instance."); //! //! let date: MockDateTime = "2020-09-12T12:35:00".parse() //! .expect("Failed to parse date."); //! //! let formatted_date = dtf.format(&date); //! assert_eq!(formatted_date.to_string(), "Sep 12, 2020, 12:35 PM"); //! ``` //! [`DateTimeFormat`]: ./struct.DateTimeFormat.html //! [`DataProvider`]: ../../icu_provider/index.html pub use icu_datetime::*; } pub mod locid { //! Language and Locale operations //! //! 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.language, lang); //! assert_eq!(loc.script, None); //! assert_eq!(loc.region, Some(region)); //! assert_eq!(loc.variants.len(), 0); //! //! let region: Region = "GB".parse().expect("Parsing failed."); //! loc.region = Some(region); //! //! assert_eq!(loc.to_string(), "en-GB"); //! ``` //! //! For more details, see [`Locale`] and [`LanguageIdentifier`]. //! //! [`UTS #35: Unicode LDML 3. Unicode Language and Locale Identifiers`]: https://unicode.org/reports/tr35/tr35.html#Unicode_Language_and_Locale_Identifiers //! [`LanguageIdentifier`]: ./struct.LanguageIdentifier.html //! [`Locale`]: ./struct.Locale.html //! [`ICU4X`]: https://github.com/unicode-org/icu4x //! [`Unicode Extensions`]: ./extensions/index.html pub use icu_locid::*; pub mod macros { pub use icu_locid_macros::*; } } pub mod plurals { //! Plural Rules operations //! //! This API provides functionality to determine the plural category //! appropriate for a given number in a given language. //! //! For example in English language, when constructing a message //! such as `{ num } items`, the user has to prepare //! two variants of the message: //! //! * `1 item` //! * `0 items`, `2 items`, `5 items`, `0.5 items` etc. //! //! The former variant is used when the placeholder variable has value `1`, //! while the latter is used for all other values of the variable. //! //! Unicode defines [`Language Plural Rules`] as a mechanism to codify those //! variants and provides data and algorithms to calculate //! appropriate [`Plural Category`]. //! //! # Examples //! //! ``` //! use icu::locid::macros::langid; //! use icu::plurals::{PluralRules, PluralRuleType, PluralCategory}; //! //! let lid = langid!("en"); //! //! let provider = icu_testdata::get_provider(); //! //! let pr = PluralRules::try_new(lid, &provider, PluralRuleType::Cardinal) //! .expect("Failed to construct a PluralRules struct."); //! //! assert_eq!(pr.select(5_usize), PluralCategory::Other); //! ``` //! //! ## Plural Rules //! //! The crate provides the main struct [`PluralRules`] which handles selection //! of the correct [`Plural Category`] for a given language and [`Plural Type`]. //! //! ## Plural Category //! //! Every number in every language belongs to a certain [`Plural Category`]. //! For example, Polish language uses four: //! //! * [`One`](./enum.PluralCategory.html#variant.One): `1 miesiąc` //! * [`Few`](./enum.PluralCategory.html#variant.Few): `2 miesiące` //! * [`Many`](./enum.PluralCategory.html#variant.Many): `5 miesięcy` //! * [`Other`](./enum.PluralCategory.html#variant.Other): `1.5 miesiąca` //! //! ## Plural Rule Type //! //! Plural rules depend on the use case. This crate supports two types of plural rules: //! //! * [`Cardinal`](./enum.PluralRuleType.html#variant.Cardinal): `3 doors`, `1 month`, `10 dollars` //! * [`Ordinal`](./enum.PluralRuleType.html#variant.Ordinal): `1st place`, `10th day`, `11th floor` //! //! ## Data Provider //! //! In order to function, the API requires data from [`CLDR`]. //! //! [`ICU4X`] is going to use a special API for handling data management called `DataProvider`. //! Until that happens, this crate will provide a simple `JSON` and `bincode` providers behind a //! flag. //! For tests and documentation examples, there is also a `DummyDataProvider`. //! //! All of the content of the [`data`] module is heavily experimental and subject to change. //! //! [`ICU4X`]: https://github.com/unicode-org/icu4x //! [`PluralRules`]: ./struct.PluralRules.html //! [`Plural Type`]: ./enum.PluralRuleType.html //! [`Plural Category`]: ./enum.PluralCategory.html //! [`Language Plural Rules`]: https://unicode.org/reports/tr35/tr35-numbers.html#Language_Plural_Rules //! [`CLDR`]: http://cldr.unicode.org/ //! [`data`]: ./data/index.html pub use icu_plurals::*; } pub mod uniset { //! Unicode Set operations //! //! This API provides necessary functionality for highly efficient querying of sets of Unicode characters. //! //! It is an implementation of the existing [ICU4C UnicodeSet API](https://unicode-org.github.io/icu-docs/apidoc/released/icu4c/classicu_1_1UnicodeSet.html). //! //! # Architecture //! ICU4X `UnicodeSet` is split up into independent levels, with [`UnicodeSet`](struct.UnicodeSet.html) representing the membership/query API, //! and [`UnicodeSetBuilder`](struct.UnicodeSetBuilder.html) representing the builder API. A [Properties API](http://userguide.icu-project.org/strings/properties) //! is in future works. //! //! # Examples: //! //! ## Creating a `UnicodeSet` //! //! UnicodeSets are created from either serialized UnicodeSets, //! represented by [inversion lists](http://userguide.icu-project.org/strings/properties), //! the [`UnicodeSetBuilder`](struct.UnicodeSetBuilder.html), or from the TBA Properties API. //! //! ``` //! use icu::uniset::{UnicodeSet, UnicodeSetBuilder}; //! //! let mut builder = UnicodeSetBuilder::new(); //! builder.add_range(&('A'..'Z')); //! let set: UnicodeSet = builder.build(); //! //! assert!(set.contains('A')); //! ``` //! //! ## Querying a `UnicodeSet` //! //! Currently, you can check if a character/range of characters exists in the UnicodeSet, or iterate through the characters. //! //! ``` //! use icu::uniset::{UnicodeSet, UnicodeSetBuilder}; //! //! let mut builder = UnicodeSetBuilder::new(); //! builder.add_range(&('A'..'Z')); //! let set: UnicodeSet = builder.build(); //! //! assert!(set.contains('A')); //! assert!(set.contains_range(&('A'..='C'))); //! assert_eq!(set.iter().next(), Some('A')); //! ``` pub use icu_uniset::*; }