Shane F. Carr
Shane F. Carr
It seems like it should be allowed for `AvailableLocales` to support `zh-Hant` but not `zh`, since `zh` implies `zh-Hans`. However, the spec currently states: > Additionally, for each element with...
It can be said that the challenge of providing i18n services can be split into two concepts: 1. **Data:** One needs access to a database of locale data. 2. **Logic:**...
ICU has a concept called "DisplayContext", which controls the capitalization rules for display names, dates, and numbers. We should consider adding support for this across ECMA 402. Discussion with regard...
I wanted to spin this off from #866, #1077, #1067, etc., in order to focus on the syntax of the options. I'll focus on date fields, time precision, and zone...
Currently, `:unit` suffers from many of the same problems as, for example, `u:locale`, explained in #1006. Since the unit being formatted is provided by the `Measure` input type (which I...
Recently, currency and unit formatting were moved to their own registry functions. However, there is still `style` that is either "decimal" or "percent". This does not make sense. Please either...
(split from #977) I really want to avoid a situation where someone writes a message using some optional extensions, and the message works in ICU4C, and then when they go...
An early decision we made in [the ICU4X design](https://docs.google.com/document/d/1X5qiEK1swGYMblwbBcOu1HkiZUbL4yhnekVyzPPQo-o/edit?tab=t.0) was that we would load data for formatters ahead of time into the built-in registry. The `u:locale` option makes this more...
registry.md says that time zone IDs are "A valid time zone identifier" with links to LDML and TZDB. However, LDML and TZDB define two different standards for time zone identifiers:...
Conflicts between time zones coming from different sources has been a persistent pain point that the Temporal champions have worked to avoid. It would be nice for MessageFormat to not...