[jira] Commented: (CONFIGURATION-345) PropertiesConfiguration does not use the default encoding to load files

["Joerg Schaible (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/CONFIGURATION-345?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12644688#action_12644688 ] 

Joerg Schaible commented on CONFIGURATION-345:
----------------------------------------------

Well, Java does not really support a special encoding for a property file. According the spec http://java.sun.com/j2se/1.5.0/docs/api/java/util/Properties.html#store(java.io.OutputStream,%20java.lang.String) a property file is always in ISO-8859-1 encoding.

> PropertiesConfiguration does not use the default encoding to load files
> -----------------------------------------------------------------------
>
>                 Key: CONFIGURATION-345
>                 URL: https://issues.apache.org/jira/browse/CONFIGURATION-345
>             Project: Commons Configuration
>          Issue Type: Bug
>    Affects Versions: 1.5
>         Environment: Win XP / Sun JVM 1.5.0_14
>            Reporter: Guillaume Darmont
>
> The piece of code
> {code:title=PropertiesConfiguration.java}
>     // initialization block to set the encoding before loading the file in the constructors
>     {
>         setEncoding(DEFAULT_ENCODING);
>     }
> {code}
> seems to set correctly the default encoding, but this block is called after "super()" in constructors.
> So when using either PropertiesConfiguration(java.io.File file), PropertiesConfiguration(java.lang.String fileName) or PropertiesConfiguration(java.net.URL url), the super() statement is called, and it loads the file without the default encoding.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.