I am using Wicket 1.4 with UTF-8 pages and properties, and I added in
my Application :
getMarkupSettings().setDefaultMarkupEncoding("UTF-8");
getRequestCycleSettings().setResponseRequestEncoding("UTF-8");
That's enough. For the localization properties files I had to use XML
properties files like this :
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE properties SYSTEM "http://java.sun.com/dtd/properties.dtd";>
<properties>
<entry key="page.title">Titre de la page</entry>
</properties>
Because Wicket uses Java Properties objects and it can't handle UTF-8.
In Tapestry they made a wapper around Java Properties so that you can
use the good old properties format (ie "key=value") with UTF8 encoding
and IMO it's a nice feature missing in Wicket.
2009/8/31 Douglas Ferguson <doug...@douglasferguson.us>:
> Excellent.
>
> I saw a bunch of emails floating around saying that you'd have to also
>
> 1) Edit connectors in server.xml and add URIEncoding="UTF-8"
> 2) Call request.setCharacterEncoding("UTF-8") (at the very beginning of the
> cycle)
>
> Are those also necessary?
>
> I'm assuming that I'll need these:
> <property name="hibernate.connection.characterEncoding">UTF-8</property>
> <property name="hibernate.connection.useUnicode">true</property>
>
>
> On Aug 31, 2009, at 5:48 AM, Tomasz Dziurko wrote:
>
> Add this to init() method in your Application class:
>
> getMarkupSettings().setDefaultMarkupEncoding("UTF-8");
> getRequestCycleSettings().setResponseRequestEncoding("UTF-8");
>
> This should be enough.
>
> --
> Regards,
> Tomasz Dziurko
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
