Shane F. Carr

I'm assuming we land on the approach in https://github.com/unicode-org/icu4x/issues/5533 where the metazone and zone variant remain calculated by icu_timezone, meaning this would still need to be in the interface between...

Hmm, I must have overlooked that algorithm in the spec. Good news though is that it is based on time zone identity rather than TZDB.

What I want to do for 2.0: - Keep both `YearMonthDay` and `Auto` styles - Rename `Auto` to `CldrLength` or similar; possibly keep it behind an experimental feature? Delete it...

The LDML spec doesn't include CldrStyle so I would like to remove it. @zbraniecki to post more info / screenshots.

OK, got it, this is just about the OS override stuff? I think the right design is to implement this in a thin wrapper that sits on top of `icu::datetime::Formatter`....

Discussed with @zbraniecki. It is solvable via either the higher-level type in ICU4X or in userland, so this doesn't need to block 2.0.

WG notes: - @nekevss How do we map style, and how do we map component fields? - @sffc - Date length: Full is Long with YMDE; Long/Medium/Short are that length...

Given the code's fairly deep integration with other types that live in `icu_datetime`, I think I share a preference for 2.

I did option 2 in https://github.com/unicode-org/icu4x/pull/5744

1-5 are all supported with current data, although we don't have an API yet for 4. But we already have a list of all canonical BCP-47 IDs in the data....