[jira] Updated: (CONFIGURATION-35) [configuration] PropertiesConfiguration.load should default to encoding "8859_1"

["Emmanuel Bourg (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/CONFIGURATION-35?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Emmanuel Bourg updated CONFIGURATION-35:
----------------------------------------

    Fix Version/s: 1.2

> [configuration] PropertiesConfiguration.load should default to encoding "8859_1"
> --------------------------------------------------------------------------------
>
>                 Key: CONFIGURATION-35
>                 URL: https://issues.apache.org/jira/browse/CONFIGURATION-35
>             Project: Commons Configuration
>          Issue Type: Bug
>         Environment: Operating System: other
> Platform: Other
>            Reporter: Will Glass-Husain
>             Fix For: 1.2
>
>
> Same issue as:
> http://issues.apache.org/bugzilla/show_bug.cgi?id=17616
> Copied from 17616
> The default load method for commons.collections.ExtendedProperties currently 
> loads properties using the default JVM encoding.  The default load() method 
> should use "8859_1" encoding.
> Rationale:
> 1) consistency: java.util.Properties.load() method always uses "8859_1"
> 2) properties resources are always 8859_1, by convention.
> 2) On edbcic machines, particularly IBM mainframes, the default encoding is 
> Cp1047 (ebcdic), but properties files are always ASCII (ISO8859-1)
> 3) This bug causes many Apache tools, such as Velocity, which uses 
> commons.collections, to fail on non-ascii machines, since they distribute 
> properties resources which are (correctly) in 8859-1.

-- 
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: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org