Shane F. Carr

Regarding options whose different values impact ICU4X data loading: - `dateFields` requires data loading. For example, it determines whether or not you need to load month names. - `length` requires...

> @sffc Given that you don't mention anything about the [override options](https://github.com/unicode-org/message-format-wg/blob/main/spec/functions/datetime.md#date-and-time-override-options) in your last comment, can we presume that those do not impose any data loading concerns? I was...

As discussed today, there are actually 3 places where information can be injected: 1. Features consistent across all locales 2. Features reachable from the locale/environment but not the input 3....

> > 1 A developer writes a message that uses datetime formatting with a Month+Day+Time field set. To format that message, ICU4X doesn't need to ship any data for era...

Note: currently, you are able to format sequence units by combining the output of Intl.NumberFormat into Intl.ListFormat. ```javascript const meterFmt = new Intl.NumberFormat("de-CH", { style: "unit", unit: "meter" }); const...

Sure, good question. 1. **API clarity:** Let's say you set `unit: ["foot", "inch"]`. Now you call `.format(71)`. What happens? Do you resolve using the smallest unit, like in my `foot+inch`...

Also a good question. From a CLDR syntax perspective, arbitrary combinations are OK. In ICU, the model I was thinking was that the .format() method would throw if the combination...

> Do we allow gaps? e.g `[hour, second]` can result in `1 hour 200 seconds`? Yeah, in this situation gaps are fine. This is not the same as #394 since...

> it may be too late It's not too late at all; the CLDR spec has not been approved yet, and even if it does, ECMA-402 could choose to do...

My understanding is that the intent is for UTS 35 to specify the correct definition of the unit when there is ambiguity (such as BTU, Cup, Barel, etc), and CLDR...