You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Howard M. Lewis Ship (JIRA)" <de...@tapestry.apache.org> on 2008/07/19 19:47:33 UTC
[jira] Updated: (TAPESTRY-2525) Properties files in a message
catalog should be read using UTF-8 encoding, rather than default encoding
[ https://issues.apache.org/jira/browse/TAPESTRY-2525?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Howard M. Lewis Ship updated TAPESTRY-2525:
-------------------------------------------
Assignee: Howard M. Lewis Ship
Summary: Properties files in a message catalog should be read using UTF-8 encoding, rather than default encoding (was: Allow different encoding for properties files)
Tapestry 4 had a more elaborate system of meta-data used to determine the encoding when reading an individual properties file. Lets see how well it works when we just assume a UTF-8 encoding (which seems to read normal ASCII files quite well).
> Properties files in a message catalog should be read using UTF-8 encoding, rather than default encoding
> -------------------------------------------------------------------------------------------------------
>
> Key: TAPESTRY-2525
> URL: https://issues.apache.org/jira/browse/TAPESTRY-2525
> Project: Tapestry
> Issue Type: Improvement
> Components: tapestry-core
> Affects Versions: 5.0.13
> Reporter: Andy Blower
> Assignee: Howard M. Lewis Ship
>
> Allow different encodings to be used for properties files so that native2ascii is not necessary. Possibly utilise the new constructors in the Java library that take a Reader. (Added in 1.6)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org