Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Fixed
-
5.0.13
-
None
Description
As discussed on the mailing list, the current approach (wherein every page may choose its own character set) leads to a number of edge-case and flow-of-control problems.
Having a single global option that is the charset for the entire application (defaulting to "UTF-8") would negate those problems, at the cost of some flexibility.
Attachments
Issue Links
- incorporates
-
TAP5-268 UTF8 characters are not supported in the autocomplete mixin
- Closed
-
TAPESTRY-2501 Form input not correctly decoded in case of non-english charsets
- Closed
-
TAPESTRY-2504 Unspecified ajax stream response encoding
- Closed
-
TAPESTRY-2537 Utf8Filter should be contributed by default in tapestry core
- Closed