ahh ofcourse the problem is that the browser doesn't sent the encoding back to the serverin which it does sent the data.That is a problem yes. Because then you need to remember per session (== browser)what kind of encoding you did set. And use that again. (also in the
WicketServlet.doGet())But i t
see http://www.wicket-wiki.org.uk/wiki/index.php/Markup_encoding and
http://www.crazysquirrel.com/computing/general/form-encoding.jspx
Juergen
On 9/6/06, Johan Compagner <[EMAIL PROTECTED]> wrote:
> what could cause problems then? It should work i think, He wants to look
> what the
> browser sent
what could cause problems then? It should work i think, He wants to look what thebrowser sent it under accept encoding and use that encoding if possibleelse use the normal default (utf-8)
On 9/6/06, Juergen Donnerstag <[EMAIL PROTECTED]> wrote:
but this is exactly what caused the problems as far as
but this is exactly what caused the problems as far as I remember. I'm
not a encodings expert, but does UTF-8 not support JIS characters?
Juergen
On 9/6/06, Johan Compagner <[EMAIL PROTECTED]> wrote:
> i think that is a global default..
>
> He does want to set the encoding based on the current re
i think that is a global default..He does want to set the encoding based on the current request.See my previous reply.johanOn 9/6/06,
Juergen Donnerstag <[EMAIL PROTECTED]> wrote:
you may remember that we lots of issues before we did that becausebrowsers behave differently. If someone would search
you may remember that we lots of issues before we did that because
browsers behave differently. If someone would search the mail archive
for wicket, there were some links to articles which nicely described
the issues associated.
>> It is already implemented The default is UTF-8 and can be configu
Maybe this line: // Determine encoding final String encoding = application.getRequestCycleSettings().getResponseRequestEncoding();in configureResponseshould be transfered into its own protected overridable method:
protected String getEncoding(){ return application.getRequestCycleSe
Thanks Jurgern.Dear Users I am confirming my experience on this issue:When I load a Link, i.e. request header referrer is null I get the configure response without the Output stream being opened. So even if I set the output stream encoding from the filter it gets overriden and it writes in the defa
On 9/6/06, Imran M Yousuf <[EMAIL PROTECTED]> wrote:
> Hi dear Users,
>
> I have a requirement that I need to cofigure the language encoding based on
> the Request Header "accept-charset". If this is not available than we have
> our default charset.
It is already implemented The default is UTF-8 a
