I went though this pain a few months ago too. Here are all the places I had
to hit:
1. In your HTML files:
<?xml version="1.0" encoding="UTF-8"?>
And also in your <head>:
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
2. For property files, if you use i18n you will need to use the foo.xml
format rather than foo.properties, and also include the above <?xml
version="1.0" encoding="UTF-8"?> in each of them.
3. In your WicketApplication.java:
// wicket 1.4; perhaps different in 1.5
getRequestCycleSettings().setResponseRequestEncoding("UTF-8");
getMarkupSettings().setDefaultMarkupEncoding("UTF-8");
4. In your pom.xml (to cover any copied resources):
<properties>
<project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
</properties>
5. Finally, in Intellij:
File -> Preferences -> File Encodings -> IDE Encoding: UTF-8.
What made this frustrating is that it always seemed to render fine with the
embedded Jetty, but not with Tomcat (so things would always look great
locally, but fall apart in production).
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/hebrew-text-looks-like-tp4260875p4271694.html
Sent from the Users forum 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
