On Wed, 07 Dec 2011 02:10:58 -0200, Robert Coie <r...@intrigue.com> wrote:
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.
Agreed! Could you post a JIRA please?
Thank you both for taking the time to reply.
We're here all week. :)
--
Thiago H. de Paula Figueiredo
Independent Java, Apache Tapestry 5 and Hibernate consultant, developer,
and instructor
Owner, Ars Machina Tecnologia da Informação Ltda.
http://www.arsmachina.com.br
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
