[TAPESTRY-2525] Properties files in a message catalog should be read using UTF-8 encoding, rather than default encoding

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 5.0.13
• Fix Version/s: 5.0.14
• Component/s: tapestry-core
• Assignee: Howard Lewis Ship
• Reporter: Andy Blower
• Created: 17/Jul/08 08:21
• Updated: 12/Feb/15 14:48
• Resolved: 06/Aug/08 17:14

Description

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)

Issue Links

• is related to: TAP5-2028 org.apache.tapestry5.ioc.internal.util.MessagesImpl should load messages with UTF-8 encoding