On 2014/05/20 (May), at 4:54 PM, Kalle Korhonen wrote:
I don't know if there's an existing issue around this.
Take a look and open a new one if no existing issues are found. Should be
straightforward to get it fixed.
Kalle
Filed:
https://issues.apache.org/jira/browse/TAP5-2346
--
Robert
As far as I can tell from reading the code, there is what seems to be a pretty
big hole in Tapestry's handling of localization.
Suppose I have set these as my supported locales: en,fr,de
...and further suppose that a request comes in with this accept-language header
klingon,de,fr
The code
The incorrect choice is because en is set as as the default locale (see
http://tapestry.apache.org/localization.html). But you are right,
accept-language allows specifying a list of desired locales, whereas it
looks like the current implementation assumes the browser to request a
single locale
