The people at my office handling translations are using a simple UTF-8 capable editor (that can be Eclipse for instance) and there is no need to escape anything when you use UTF-8 in the properties files. That's much more comfortable when working with arabic or chinese, because people can read without unescaping, and they can also use a diff tool.
The point I was raising is that when working on a Tapestry application, people at my office are used to have a simple property format, and you can do this because they made a wrapper around native Java Properties that can handle UTF-8 in properties file. When I switched to Wicket and XML properties files, they complained that it was much more verbose for no gain. And I don't have any objections to this statement. Doing the same thing with Wicket should be easy, basically it should consists of changing the method : PropertiesFilePropertiesLoader.loadProperties(BufferedInputStream in) defined in PropertiesFactory class to *not* use Java Properties directly but instead fill a new Property object from an InputStream. And the InputStream should honor the application encoding set in the Application settings, which in our case is UTF-8. And you return Properties like before. That's it. See : http://tapestry.apache.org/tapestry4/tapestry/apidocs/org/apache/tapestry/util/text/LocalizedProperties.html 2009/9/1 Wojciech Żaboklicki <zabia...@gmail.com>: > Man, use the native2ascii built-in JDK tool. > It's very simple, transforms your messages into ASCII escaped. > > Regards, > Wojtek > > Olivier Bourgeois pisze: >> >> That's exactly what I said : I had to use XML properties files to have >> UTF-8 localized properties. >> >> You can't use simple properties format because Java can't handle >> natively anything else than ISO. We use also Tapestry here, and you >> can use UTF-8 properties files (thanks to the wrapper around native >> Java properties). >> >> XML files are allright, but they are definitively verbose. >> >> 2009/9/1 Eelco Hillenius <eelco.hillen...@gmail.com>: >> >>>> >>>> Erm.... >>>> http://chillenious.wordpress.com/2006/11/13/wicket-now-supports-resource-bundles-in-xml-format/ >>>> >>> >>> Which says Wicket 2.0 (yes, it's that old), but it was also one of the >>> first things backported. Loading is automatic, and .xml takes >>> precedence over .properties. >>> >>> Eelco >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org >>> For additional commands, e-mail: users-h...@wicket.apache.org >>> >>> >>> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org >> For additional commands, e-mail: users-h...@wicket.apache.org >> >> > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
