Hi Stephan,
Hmm I'm not sure. If you visit this example page, do you get English messages or German? On that
page, if I switch my browser language to English I see English and for German I see German messages.
Did you perhaps reconfigure Click in any way?
In your page you could also put a breakpoint and print out the value of getContext().getLocale() and
confirm it is English.
http://click.avoka.com/click-examples/form/standard-controls-form.htm
Kind regards
Bob
On 2013/05/03 16:21, Kennedy, Stephan wrote:
Hi
I'm wondering why I only get German strings in my web page, given I am handling
i18n as explained in
the documentation.
Both click-page.properties and click-page_de.properties exist, the click.xml
does not specify a locale.
When I delete an entry from click-page_de.properties the english text is used
instead, so obviously
both files are being found.
The texts already provided by click (e.g. when textfield content is missing for
a mandatory text) do
seem to switch to the language configured in the browser and sent in the
request.
I'm using click 2.2.0.
The request sent by the browser looks like this:
POST /telnumlookup/ldapentries.htm HTTP/1.1
Host: 172.29.129.1:8080
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:20.0) Gecko/20100101 Firefox/20.0
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
*Accept-Language: en-us,en;q=0.5
*Accept-Encoding: gzip, deflate
DNT: 1
Referer: http://172.29.129.1:8080/telnumlookup/ldapentries.htm
Connection: keep-alive
Content-Type: application/x-www-form-urlencoded
Content-Length: 58
HTTP/1.1 200 OK
Server: Apache-Coyote/1.1
Expires: Thu, 01 Jan 1970 00:00:00 GMT
Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
Pragma: no-cache
Content-Type: text/html;charset=UTF-8
Transfer-Encoding: chunked
Date: Fri, 03 May 2013 09:30:52 GMT
etc.
Any ideas how I might track this down?
Stephan
