You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by hl...@apache.org on 2008/07/29 22:50:54 UTC
svn commit: r680840 - /tapestry/tapestry5/trunk/src/site/apt/upgrade.apt
Author: hlship
Date: Tue Jul 29 13:50:54 2008
New Revision: 680840
URL: http://svn.apache.org/viewvc?rev=680840&view=rev
Log:
TAPESTRY-2543: Simplify Tapestry to use UTF-8 (or another, configurable character set) across the entire application
Modified:
tapestry/tapestry5/trunk/src/site/apt/upgrade.apt
Modified: tapestry/tapestry5/trunk/src/site/apt/upgrade.apt
URL: http://svn.apache.org/viewvc/tapestry/tapestry5/trunk/src/site/apt/upgrade.apt?rev=680840&r1=680839&r2=680840&view=diff
==============================================================================
--- tapestry/tapestry5/trunk/src/site/apt/upgrade.apt (original)
+++ tapestry/tapestry5/trunk/src/site/apt/upgrade.apt Tue Jul 29 13:50:54 2008
@@ -20,6 +20,13 @@
Properties files in message catalogs are now already read using the UTF-8 charset. Unlike traditional
Java ResourceBundles, it is <not> necessary to use Java's <<<native2ascii>>> tool.
+* {{{https://issues.apache.org/jira/browse/TAPESTRY-2543}TAPESTRY-2543}}
+
+ TAPESTRY-2543 simplifies Tapestry's approach to localization, as it pertains to
+ output and request character encodings. Previously, each page could be configured with a different character
+ encoding, which causes a number of problems related to Ajax and file upload requests. A single
+ application-wide character encoding is now used, by default UTF-8.
+
Release 5.0.13
As part of {{{https://issues.apache.org/jira/browse/TAPESTRY-2311}TAPESTRY-2311}}, there have been