Closed OliverJAsh closed 2 years ago
The counter-argument in terms of correctness is that this could be {numberOfPhotos, number}
.
I see three options:
This also touches upon the broader question of whether and how we should favour correctness or acceptance (for want of a better word - think HTML in browsers). Vaguely related: #9, #27
One possible approach:
lint
subcommand that can lint against inefficient or otherwise suboptimal stuff like the above. This should be fairly straightforward analysis of the AST.format
subcommand which would in practice just rewrite spacing and ordering of interpolation tokens; think Prettier for our ICU messages. Probably blocked by #47.The first point gives translators maximum flexibility. The latter two allow us to maintain correctness in our master translations.
What should we do if there are two other
wildcard cases? I think that should still error as the translator's intent is unclear?
Yeah agreed!
select
. plural
and selectordinal
remain.
Some languages might only have one plural form.
E.g. cardinal. We send:
They return:
E.g. ordinal. We send:
They return:
Currently
intlc
throws if the only case isother
: