Skip to content

Commit

Permalink
Introduce why we need LocaleFallbackProvider
Browse files Browse the repository at this point in the history
  • Loading branch information
sffc committed Aug 26, 2023
1 parent 87058d8 commit bc8002f
Showing 1 changed file with 4 additions and 0 deletions.
4 changes: 4 additions & 0 deletions docs/tutorials/data_management.md
Original file line number Diff line number Diff line change
Expand Up @@ -46,6 +46,10 @@ You should generate it automatically at build time if:

If you check in the generated data, it is recommended that you configure a job in continuous integration that verifies that the data in your repository reflects the latest CLDR/Unicode releases; otherwise, your app may drift out of date.

## Locale Fallbacking

Data generated with `--format blob` or `--format fs` supports only exact matches for locales, not locales requiring _fallback_. For example, if `en-US` is requested but only `en` data is available, then the data request will fail. Because of this, it is often desirable to configure a `LocaleFallbackProvider`, as illustrated in the remainder of the examples on this page.

# 3. Using the generated data

Once we have generated some data, it needs to be loaded as a data provider. The blob format we chose can be loaded by `BlobDataProvider` from the `icu_provider_blob` crate.
Expand Down

0 comments on commit bc8002f

Please sign in to comment.