Shane F. Carr

Well, we have already been shipping `Date`, `Time`, and `DateTime` since 2021. `ZonedDateTime` is simply the natural extension of that. Users of ICU4X will probably be looking for a type...

Just to highlight this in case it's not obvious: everything we're talking about is namespaced. - `icu::calendar::Date` - `icu::calendar::Time` - `icu::calendar::DateTime` - `icu::timezone::ZonedDateTime` So there's no ambiguity that you are...

> My strong opinion is that we should not use ZonedDateTime for a type that only provides a partial (formatting only) implementation of ZDT's features in JS and Java. ICU4X's...

Responding to the following comment from @macchiati > What might work is for unit is to only require a small subset of unit ids to be supported. Then ICU4X and...

`:unit unit=meter` is fine. Where it breaks is if the unit is specified by a `Measure` input (which is a good choice, but it makes data slicing harder).

The full list of quantities are those found in [units.xml](https://github.com/unicode-org/cldr/blob/main/common/supplemental/units.xml). ICU4X unit formatting is very much under construction, but you can follow along at https://github.com/unicode-org/icu4x/issues/6161 We know that `percent` is...

In the ICU4X TC, we've been working in the direction of slicing units by their quantity because: 1. The number of quantities is much smaller than the number of units,...

Let's look at these four ways to use `:unit` in terms of inputs: 1. The message specifies the unit, and the input is Number-like 2. The input is Measure-like, and...

Opting-in the extensions makes it clearer what messages your formatter is _capable_ of processing. Enabling `extensions: ["calendarOption"]` does not mean that the messages being processed _must_ utilize that extension. But...

I wouldn't find it as elegant, but an alternative that aligns with my problem statement would be to basically have a MessageFormat Validator, like the W3C HTML Validator, that checks...