Addison Phillips

Moving this to registry, since the number functions are where this is defined. The WG consensus in 46.1 is that we're fine with integer selection being well-defined with implementations allowed...

Moving to 48

Can you clarify what you mean by "language subtag"? I assume you mean **_primary_** language subtag? From the context and from @hsivonen's bug, I gather that this does mean the...

Thanks @zbraniecki. I understand about ICU4X's optimizations. I agree that there are no _valid_ primary language subtags of 4 to 8 characters (even in the grandfathered set, although one could...

@zbraniecki I'm beating a dead horse here, but... At least on some browsers, the tag `english-ohio-us` works. This tag is quite obviously not valid, but it is well-formed. The tags...

There can be only one response to that:  https://xkcd.com/927/ 😁 In practice, there is no practical difference between all of these locale identifier regimes. BCP47 has quirks. ULIs have...

@Manishearth That description seems to be of what UTS35 calls a [unicode_bcp47_locale_id](https://www.unicode.org/reports/tr35/tr35.html#unicode_bcp47_locale_id). The differences are found [here](https://www.unicode.org/reports/tr35/tr35.html#BCP_47_Conformance). The primary leftovers if you use that instead of `unicode_locale_id` are: - The...

(as individual contributor) This specifically breaks a long time design tenet. We try to avoid features that are "string concatenation in disguise". I am strongly opposed to this.

(chair hat on) We need to determine if this is in or out for LDML45. (as contributor) To bring it in, we would need to add `quoted-pattern` to `local-declaration`. The...

@stasm will document why we will not do this. (from 2024-02-12 call)