Since a few days, Wicket (2.0) supports loading properties in the XML format that Java supports since version 5. The great advantage of this is that you can maintain your localized messages in any encoding you like, without having to do ugly things like using the unicode escpace codes.
As a bonus I converted Wicket 2.0’s examples to use just one HTML file, and use message bundles (both properties and xml format) for all the localized strings. This is a much better pattern then using a separate HTML file for each locale.
Check out 2.0’s FormInput example to see for yourself.
