Shane F. Carr

@macchiati was making an argument that formatting a percent is actually a formatting hint. "0.5 = 0.5 = 50% != 0.5%". Even in this case, the name "style" is something...

> The name `style` is taken directly from `Intl.NumberFormat` (as noted in the document). I don't buy this argument because `style` is a toggle between unit, currency, percent, and decimal...

This is not fixed, and registry.md says "The following options and their values are required to be available". So please fix this before LDML 47.

TG2 discussion: https://github.com/tc39/ecma402/blob/main/meetings/notes-2024-02-22.md#decimal-integration-856

I'm a bit conflicted about `timePrecision`, which is encoded as an option in the data model, but it is more intuitive to think of it as part of the field...

> Does ICU4X support formatting a date with a timezone, but no time? And if so, why? It does. I pushed back a bit on this but was convinced that...

> There's no need for us to play code golf here, and so I'd prefer spelling out the names rather than using one-letter abbreviations A major issue we avoid by...

> > For example, one might say that last month's TC39 meeting was "28th - 30th May 2025, Central European Summer Time". > > Is there any real-world example of...

I'd be satisfied with something like this: ``` # Standard Form {$input :date fields=year-month-day} {$input :date fields=month-day-weekday} {$input :time fields=hour-minute} {$input :time fields=hour-optional-minute} {$input :time fields=hour-minute-second} # Concise Form {$input...

> > But, if you believe there is a strong motivation to change the spec to make zone a time field and prevent it from being combined with a standalone...