Restarting the browser was somehow responsible. That is, if you don't
restart the browser between locale changes they don't get picked up.
nl_NL works fine.
Question: is this caching caused by the browser or Wicket? I seem to
remember the Wicket code assumes the locale doesn't change during the
session. Is that true?
Gili
Gili wrote:
Hi,
I wanted to add a Dutch version of my website so I created a file
Page_nl_NL.html like the one in wicket-examples then changed my locale
in FireFox to dutch (which it labeled solely as "nl").
This didn't work (the Dutch version of the page wouldn't display
when I hit it). I then renamed the filename from _nl_NL to _nl and it
fixed it. Any idea why? Will _nl.html act as a catch-all for all "nl"
locales unless a style-specific file exists? That is, if I have
page_nl.html and page_nl_NL.html will the former catch all "nl" locales
except nl.nl?
Thank you,
Gili
--
http://www.desktopbeautifier.com/
-------------------------------------------------------
SF.Net email is sponsored by:
Tame your development challenges with Apache's Geronimo App Server. Download
it for free - -and be entered to win a 42" plasma tv or your very own
Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php
_______________________________________________
Wicket-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-user
