Eemeli Aro

I talked with @sffc while we met in person this past week, and it came up that ICU4X would almost certainly want unit formatting to be separated by category. As...

> If we split date, time, and datetime into individual functions, why would we not do the same for the zoned versions? I'd say it's because the timezone is a...

Without a time, a date is describing a whole day or an even wider range. With a time, we're describing a specific instant. We speak of them differently. So for...

Another unused sync feature that we could/should remove: having more than one target repository.

Support for more than one target repository (per-locale or otherwise) was removed in #3312.

Not quite, without options the year uses four digits: ```js new Intl.DateTimeFormat('en').format(new Date) // '7/1/2024' new Intl.DateTimeFormat('en', { dateStyle: 'short' }).format(new Date) // '7/1/24' ``` And it's by no means...

> include the [design document](main/exploration/default-registry-and-mf1-compatibility.md), not just the registry This PR includes updates to the design doc as well. > JS's APIs and ICU's APIs are good influences to look...

> That is, instead of choosing which `dateStyle`/`timeStyle` is default, we should say: > * `{$dt :datetime}` is equivalent to `{$dt :datetime year=numeric month=short day=numeric hour=numeric minute=numeric}` > * `{$d...

For the tech preview, I'm starting to think we probably ought to restrict the literal values for each of `:date`, `:time`, and `:datetime` to only support a full date+time string....

As one minor relaxation, we could also support plain yyyy-mm-dd dates, as long as they did not include timezones. That's valid ISO 8601, and when used as a literal it's...