Addison Phillips

I generally keep the next version label on low-priority items and push them to the following release if they go unaddressed. Alternatively, I don't have a 48 label yet, but...

This mechanism looks decent, but I don't think we should incorporate it. We do need to point to CLDR data (which this PR doesn't solve). I think that recreating plurals.xml...

> Currently, in order to figure out that in Polish a selector on :integer will never select other, you need to parse the [syntax](https://www.unicode.org/reports/tr35/tr35-53/tr35-numbers.html#Language_Plural_Rules) used within the elements. That's certainly...

@stasm I agree that the purpose of the registry data (as I've described it elsewhere) is to inform tools and such about available variant keys, but *not* to replicate either...

In the 2024-01-15 call we agreed to tag this for `Future` and that I would set up a separate call about registry format.

@domenic The US isn't the world. There exist different cultural conventions regarding titlecasing, even within English. If the JS standard library function `toTitleCase()` only serves US English booktitle's idiosyncratic needs,...

@domenic Ah, I get it. Still, most functions that claim to "titlecase" in other programming languages are algorithmic and fail to get US English titlecasing correct either. To your point,...

@leobalter `capitalize` is not "universal" and does depend on locale in exactly the same way that upper/lower/titlecasing does and for [the same reasons](https://www.w3.org/TR/charmod-norm/#definitionCaseFolding). The point of doing `capitalize` instead of...

@emlun That's a great callout. I filed a tracking issue and will work on getting that published in String-Meta ASAP

@sffc noted: > An additional ergonomic issue with :date and :time is that it temps people to write messages such as {$input :date} at {$input :time} instead of {$input :datetime}....