Affects Version/s: 5.0.13
Fix Version/s: 5.0.14
This problem occurs because major browsers don't conform to standards which says that client charset should be sent via "content-type" HTTP header to server.
Everything is well described in this article:
I guess this is closely related to submitted issue:
So, fix should be that
HttpServletRequest.setEncodingCharset("UTF-8"); (I guess charset should be configurable somehow)
is set in tapestry filter prior to anyone fetching any parameter value.