The problem is that with any other form fields, what is saved in my models is fine. All the accentuated characters are fine. If I output (in a log file for example) the content of a string field, I can see the accentuated character. But with the AutocompleteTextField, if I try to do that in the "getChoice" method, the "input" parameter output is still "encoded". So I am unable to compare the string with what I have in my db.
You say that it is actually UTF-8 in the request. Good that is what I thought first, but why in the java code it is not interpreted correctly? >From what I remember, Java string are always in UTF-8. No? Thierry On Mon, Mar 23, 2009 at 10:30, Michael Sparer <michael.spa...@gmx.at> wrote: > > it isn't the 'wrong character' it's é in UTF8 which is perfectly fine -so > you > end up with an é at the end of the line - so what's the problem again? :-) > > regards, > Michael > > > tleveque wrote: > > > > Hi, > > > > I have a problem AutoCompleteTextField and accentuated characters. When I > > type characters within the us-ascii set, there is no problem, but as soon > > as I use other characters (like 'é'), it doesn't work. The wrong > character > > is received. > > With the Ajax debugger I can see that what is sent is wrong (or maybe > > encoded?). For a 'é', it sends is '%C3%A9'. That what is received as the > > parameter of the "getChoices" method. > > > > Is there something I can do about that? > > I am using Wicket 1.3.5 > > > > Thanks... > > > > > ----- > Michael Sparer > http://techblog.molindo.at > -- > View this message in context: > http://www.nabble.com/AutoCompleteTextField-and-accentuated-characters-tp22637037p22661278.html > Sent from the Wicket - User mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > >
