Shane F. Carr

Decision from 2023-11-09: - icu_locid stays as is - icu_locid_transform becomes the lower level crate - Revive icu_canonicalizer to become the higher level crate See full notes in the 2023-Q3...

The consensus from 2023-11-09 was to use the name `icu_canonicalizer`, but the revivable crate is named `icu_locale_canonicalizer`: https://docs.rs/icu_locale_canonicalizer/latest/icu_locale_canonicalizer/ I remember that I did not really like this name from the...

My agreement to the previous consensus was based on the understanding that `icu_canonicalizer` was the name of the previous crate. Given that it is actually `icu_locale_canonicalizer`, the consensus is not...

I would love to hear a suggestion for a better name for the higher-level crate. Here are the only ones I've seen: - `icu_locid_utils` - `icu_canonicalizer`

It's named `icu_locid` because in ICU4C there is `locid.h`, and because the name `icu-locale` was claimed in kebab case and we can't get it back in snake case. I could...

Hmm. What do you think about `icu_core`? Everything can depend on it and it can include `Locale` and anything else we need to truly share across all components such as...

So the crates could be: - `icu_core` = contains Locale, LanguageIdentifier, and internal macros for things such as logging and documentation. We will try to keep it as small as...

- `icu_fallback` - `icu_locale_fallback` - `icu_locale_ops` - `icu_locale_data_utils` - `icu_locale_support`

The first round of voting didn't reach a clear consensus. I'll send out another ballot with these options: icu_locale_fallback icu_locale_ops icu_locale_support icu_locale_util (added late)

ICU4X WG discussion from 2024-04-18: - @leftmostcat - What immediately strikes me is that you could have option 5 (four small crates) with feature-driven re-exports - @sffc - The only...