I am having the same problem. did you had any luck with it?
no, sorry, no answers and I've found no work-around yet. It's a pity because I can't do without accent... I'll post a reply if I find something, hope you'll do it too if you find. :)
Does the browser detect the UTF-8 encoding? (See what's checked in the Caracter encoding menu in the browser when viewing the page)
Also check the generated html.
May be you can add this in the head tag of the pages to make sure it's detected properly:
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
Sometimes, it's also required to have set properly.
*Sometimes, it's also required to have this:
Thanks for your help,
the browser seems to detect the UTF-8, no problem. I've already the charset in the meta tag, I've tried to add the html lang="fr" but it changes nothing.
Is it normal that I don't see the character-encoding-filter tag in http://jboss.com/products/seam/web-1.2.xsd ? Can it be the reason for which it doesn't work?
Also, should the line in components.xml be sufficient to make it work or is it better to put the filter in web.xml?
I take it you've got the Seam Filter installed in web.xml?
Yes, I've got the seam filter and I've added the encoding filter (the lines quoted in my first post).
I've tried to remove the seam filter and let just the encoding filter to see what happens but it doesn't change anything.
Just an answer to pull up this important *bug* for french people.
Exactly the problem I have at this time.
The only thing you really need is
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
as stated previously. It is always used by the browser to sent request to the server. Even if the encoding option of the browser is forced to an other value.
The attribut "lang" in tag "html" is not related to the charset but to the presentation options for date, currency, number...
I've never had any problem with english/french applications. I let the browser and server switch between the two of them. I don't use any CharacterEncodingFilter. At least it must be used without "overrideClient" parameter unless you're sure at 100% that all the pages sent to the browser are in the same charset that the one specified.
The last time I got such issue, it was related to a database server which was configured with a charset different of the one specified in the web pages.
ok thanks for the message I will try to modify the charset of my DB.
But the problem comes from the encoding in the href element.
The problem might arise from URIEncoding http://www.jboss.com/index.html?module=bb&op=viewtopic&t=107804 will address your problem. This is only applicable when your request parameters are sent with the URL query string.
One other possibility of this happening is your database's client/server character encoding. For Oracle, one way of configuring your client encoding is with setting NLS parameters accordingly.
You're right Ramazan, adding <useBodyEncodingForURI="true"> in my server.xml solved my problem.
Thanks a lot!