Gilberto, Thank you for the explanation and the link, I did assume that what I 
see on avoka and on my site is not a problem rather a result of the out-of-box 
configuration. As you suggested I would probably stick to set-up my site with 
one locale - that would do the trick in my case!
 
Once again, thank you for the help and all the best!
 
Regards
 
Tamas
 
Date: Mon, 5 Aug 2013 15:06:29 -0300
Subject: Re: Paginator language detection issues
From: [email protected]
To: [email protected]

Tamas, I think there are no problem with the example and your app. The 
inconsistency you see, mainly on click examples, is that all the examples are 
in English, but all the controls has their own internationalization file and 
when you reach the site with your on language the controls render in your 
locale but the site always on English.

However, you can make you site just with one locale [1]. 

Regards,

Gilberto

[1] http://click.apache.org/docs/user-guide/htmlsingle/click-book.html#click-app



2013/8/3 Tamas Balazs <[email protected]>




Dear Apache Click Team,
 
I wonder if you could shed some light/give me some pointers from where I can 
tailor the framework accordingly - I currently have some issues with the table 
paginator object. When I visit the avoka example site with my girlfriend's 
computer (Windows Vista with traditional Chinese) at the Column Panel demo the 
paginator comes in with traditional Chinese characters whilst the whole site is 
English. I implemented a similar structure on my web-server and the issue has 
replicated itself, the only difference was that my server does not support 
traditional Chinese yet, thus the paginator was full of question marks as usual.

 
Would you know how to fix up the language/characters at the table paginator 
object as I would like to keep some sort of language consistency on the 
web-interface of my application without having any relation to the visitor's 
language settings at their operation system level.

 
Any advise will be highly appreciated.
Regards
 
Tamas 
                                          

                                          

Reply via email to