> 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.
Erm.... http://chillenious.wordpress.com/2006/11/13/wicket-now-supports-resource-bundles-in-xml-format/ Eelco --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org