Eemeli Aro

> If we also chose to forbid fractional keys in `:number`/`:integer`, that would go a long way towards simplifying the problem. I'd be fine with that. We'd need to find...

> I support the idea of allowing matches in these functions, if we can figure out a way to do so reliably. That means defining how a key like `1.5`...

> The selection process *must not* use the resolvedSelector, if that value is > 1.5003 while the formatted value is "1.5" (or equivalent in native format). > It must instead...

@aphillips I think we're arguing about corner cases that don't actually exist. Of the keys in the table you show, the only ones I can believe will ever show up...

> Anyway, you asked for an example. Driving directions are always good for arbitrarily chosen numbers bigger than 10: [...] Ugh, that's ugly, I did not consider that `maximumSignificantDigits` could...

One example of the type of situation I'm describing is JavaScript, which provides Intl.NumberFormat and Intl.PluralRules as two separate APIs. Together, they allow for proper number formatting as well as...

> This is good, but I think we should also do leading whitespace. From my implementation experience, this is a trivial to implement and can be implemented to be as...

Currently, Pontoon wins in this case. @mathjazz Do you still think that the reverse should hold?

Within the next few months, I'll be adding linting/validation support to [moz.l10n](https://github.com/mozilla/moz-l10n/), to replace the current plethora of bespoke L10n linters we use, including e.g. moz-fluent-linter. This will support all...

@stevejalim Would it be possible to get your requirements/expectations enumerated somehow? That would make it much easier to ensure that the moz.l10n linter will serve your needs from the start.