On 8/28/13 1:12 PM, Anne van Kesteren wrote:
On Wednesday, February 27, 2013 12:28:43 PM UTC, Axel Hecht wrote:
That's rather orthogonal to what you're currently trying to do, but it's
also indicating to me that we should remove all of those settings from
intl.properties, and just leave accept-lang, and deduce the rest.
So how about the parser just accepts a locale value and implements the
locale-to-fallback encoding map? Given the numerous problems discovered[1],
locale-defaults actually being part of the HTML Standard, and it being
available as option to change encourages people to tweak it, I think that would
be a better way forward.
I don't think that 'a locale value' is correct. We should use content
languages and not UI language. But from the list of preferred content
languages, we can help the parser. It is a bit more tricky in general
than we have right now, as for some users, we'll end up with mismatches
between the fallback encodings. We could just use the first language for
which we have one, though. At least as first step.
I don't know which locale-defaults are part of the html spec, before I
read it all, can you elaborate?
I wonder if there are similar settings that are in a sense too technical to
leave up to localization teams.
We have a few. We're trying to set them up these days such that garbage
values mean en-US default, and provide patches and edits for the others.
Axel
[1]Recent issues discovered by hsivonen:
* https://bugzilla.mozilla.org/show_bug.cgi?id=910163
* https://bugzilla.mozilla.org/show_bug.cgi?id=910165
* https://bugzilla.mozilla.org/show_bug.cgi?id=910169 (bogus value, even)
_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
