bug 258246: RFC: Accept language header: 'en-gb' and matching of templates/en/
Tobias Burnus
burnus at gmx.de
Tue Sep 7 10:35:16 UTC 2004
Hello,
since this a kind of FAQ regarding bugzilla-de, which is frequently set
up as languages=de,en and defaultlanguage=en, I'm thinking of changing
the current accept-languages--languages matching.
See also bug 258246, http://bugzilla.mozilla.org/show_bug.cgi?id=258246
------------------------------------
Current behaviour:
HTTP ACCEPT LANGUAGES: en
matches templates/{en,en-gb,en-us,en-gb-cockney}/
HTTP ACCEPT LANGUAGES: en-gb
only matches templates/{en-gb,en-gb-cockney}
This is according to the specs:
# Per RFC 1766 and RFC 2616 any language tag matches also its
# primary tag. That is 'en' (accept language) matches 'en-us',
# 'en-uk' etc. but not the otherway round. (This is unfortunally
# not very clearly stated in those RFC; see comment just over 14.5
# in http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.4)
And makes sense, but it is not very intuitive.
Being in Germany I'd set 'de-de' in the browser. The w3c's comment
suggest that
the browser then ask to add/automatically adds 'de' as well. But for
instance
Mozilla doesn't do this.
The question is: Should we change the behaviour of Bugzilla? That is
'en-gb' should match 'en' (and (?) 'en-*'?). Should this be optional? Or
what is
the right (TM) way to proceed?
I currently recommend:
ln -s de de-at
ln -s de de-be
ln -s de de-ch
ln -s de de-de
ln -s de de-lu
and "languages = de-at,de-be,de-ch,de-de,de-lu,en", defaultlanguage=en
But this is quite cumbersom.
------------------------------------
One option would be to add a boolean option to defparams.pl. Any better
ideas?
Tobias
More information about the developers
mailing list