On Tue, Dec 06, 2011 at 04:49:42PM -0800, Kalle Korhonen wrote: > What's your JVM's file.encoding set to? (e.g. -Dfile.encoding=UTF-8). > The default for most JVMs is *not* UTF-8. Tapestry assumes UTF-8 > throughout. I believe it's US-ASCII, as checked by Charset.defaultCharset(), although I have seen some other reports indicating that that may not be reliable due to caching. It's not "my" JVM in the sense that I can't change the settings - it's at the mercy of Google App Engine.
On Tue, Dec 6, 2011 at 4:58 PM, Thiago H. de Paula Figueiredo <thiag...@gmail.com> wrote: > I configure my IDE to edit all files as UTF-8 to avoid problems and > have > consistency at the same time. So do I. The file is UTF-8, and when the application is run under the local appengine simulator, the Charset.defaultCharset() check mentioned above indicates UTF-8. I just think it would be preferable if Tapestry could eliminate all behavior reliant on the JVM's default charset. Thank you both for taking the time to reply. -- Robert Coie Implementor, Apropos K.K. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
