Addison Phillips

You might want to start by looking at what Unicode and ICU have done in this space. For example, the [UnicodeSet](https://unicode-org.github.io/icu-docs/apidoc/released/icu4j/com/ibm/icu/text/UnicodeSet.html) class in ICU4J is similar to the kinds of...

@fantasai It's [here](https://www.w3.org/2022/09/12-i18n-minutes.html) in our TPAC minutes--almost exactly as you remember it :-). Search for the word "hide" and the conversation proceeds from there.

CSS will ping I18N when text is written for review by CLREQ

I18N recommends that trim-end be the default. See about [here](https://www.w3.org/2022/09/13-i18n-minutes.html#t09)

As discussed at TPAC, I18N has *no objection* to secure payment confirmation proceeding to CR on the understanding that was progress is made with TC39 (etc) changes can be picked...

@domenic I hear that ☹️. I will take it up with ECMA-402, et al. As an alternative, do you think there's a way for us to provide optional elements here,...

@domenic Java has some (quite old and not-well-designed) support for localizable exceptions. I've done quite a lot with building localizable exception support in different frameworks in that language as a...

`DOMException` has `name`, which behaves as a locale-neutral identifier (the fact that it's a string is fine--it just basically functions as an open-ended enum). I'm totally cool with `name` and...

Writing code that depends on a localizable value is a basic I18N anti-pattern. I don't disagree with you: some people's code probably does depend on the non-localization of some `message`...

Most developer's initial intuition is that Exceptions are "meant to be consumed by developers". In that case the localization of the message makes it an even greater pain in the...