On 22.02.13 15:37, Henri Sivonen wrote:
I've been finding and, to a lesser extent, reporting and writing
patches for bugs where a localization sets the fallback encoding to a
value that doesn't suit the purpose of the fallback. In some cases,
there such bogosity in the intl.properties file (e.g. translation of
the word "windows" as part of a charset label) that I suspect that
changes to intl.properties have been landing without review.
I propose we adopt a rule that says that localizations need review
from the HTML parser module owner (i.e. me) to change the values of
preferences that modify the behavior of the HTML parser. (In practice,
this means the localizable properties intl.charset.default and
intl.charset.detector.)
Opinions?
I don't think that .platform is the right group to discuss policies for
l10n, tbh.
Anyway, I don't think that it requires your review. For one, these rules
just don't work in practice. We're facing the very same problem with
search engines. There's just no other way than post-mortem work. That's
one of the reasons why we're not taking arbitrary changesets to ship to
any audience beyond aurora and nightly, for beta and release, we got to
have technical checks in place.
I usually catch regressions to intl.properties when reviewing requests
for updates to those changesets.
That said, I don't know what intl.charset.detector should be set to,
aside from nothing. Looking at your patch, the comment doesn't make that
clearer, too, I'll follow up there.
Axel
_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
