Addison Phillips

Results 457 comments of Addison Phillips

Section 20.7.1 has a minor error where it says: ``` A Unicode code point escape lets us specify a code point hexadecimally (1–5 digits). It produces one or two JavaScript...

Note that FSI/PDI (and other isolating controls) have weak support in browsers currently (see https://w3c.github.io/i18n-tests/results/bidi-algorithm#rli_etc). I get very poor results with isolating controls in Chrome, for example. Here's Chrome (left,...

@zbraniecki Actually, I do mean *all* placeables--and especially the ones that involve placing strings inside of other strings--so precisely StringLiteral, MessageReference, and maybe TermReference. We try to illustrate the problems...

@cristisilaghi Note that CLDR provides different contextual strings for "standalone" vs. "in context" display of strings like language, region, time zone name (or other values, such as month names, etc.).

Hmm... these examples (and this syntax) promotes a common I18N mistake: the idea of sentence concatenation working equivalently across languages. This example assumes that the user name always occurs after...

@eemeli The reasoning isn't visible in English: the `one` rule fires in some locales for numbers ending in 1 (21, 31, etc.). The `1` rule fires for the value ==...

@Pike a nit: while currencies have a specific number of fraction digits, there are *many* applications (particularly currency conversions) in which one needs to ensure that greater precision is maintained---and...

@msporny Thanks. We know you're not responsible for external standards. Generally, we prefer that examples that don't draw on some specific external standard (i.e. invented values) not exemplify I18N anti-patterns....

In an [email reply](https://lists.w3.org/Archives/Member/member-i18n-core/2021Nov/0023.html) to @wseltzer I remarked: When we last spoke, I took an action item to produce a PR with suggested text. I prepared that PR and you...

I drew an [action item](https://www.w3.org/International/track/actions/1213) to reply directly to @xorgy's comment. The short answer is: the mechanism isn't "truly broken" from the point of view that one could use it...