Re: String encoding in activation context

er according to https://issues.apache.org/jira/browse/TAPESTRY-2710?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12640867#action_12640867 I should have used any different encoding - not url... Shouldn't it be a Tapestry's responsibility? For me it's inconsistency in Tapestry'

String encoding in activation context

. Application source and output encoding is set to UTF-8. thanks in advance for any help. Shymon -- View this message in context: http://www.nabble.com/String-encoding-in-activation-context-tp20075742p20075742.html Sent from the Tapestry - User mailing list archive at Nabble.com.