You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@commons.apache.org by "Ats (JIRA)" <ji...@apache.org> on 2013/03/31 21:27:15 UTC

[jira] [Commented] (CONFIGURATION-538) Saving PropertiesConfiguration using UTF-8 encoding doesn't work

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

Ats commented on CONFIGURATION-538:
-----------------------------------

If private methods of org.apache.commons.configuration.PropertiesConfiguration.PropertiesWriter would be changed to protected, then it would be easier to plug in custom PropertiesWriter(that wouldn't escape non ISO-8859-1 characters) via 
propsConf.setIOFactory()
without reinventing the wheel (copying too much existing code from existing classes).
                
> Saving PropertiesConfiguration using UTF-8 encoding doesn't work
> ----------------------------------------------------------------
>
>                 Key: CONFIGURATION-538
>                 URL: https://issues.apache.org/jira/browse/CONFIGURATION-538
>             Project: Commons Configuration
>          Issue Type: Bug
>    Affects Versions: 1.9
>         Environment: shouldn't be important, but 64bit Windows 7
>            Reporter: Ats
>              Labels: PropertiesConfiguration,, charset, encoding,, save
>
> I created JUnit test http://goo.gl/GCwi2, that uses two methods to save PropertiesConfiguration (with property value containing utf-8 characters) into file:
> 1) propsConf.save(file); // propsConf.setEncoding("UTF-8") was called before
> and
> 2) propsConf.save(fileOutputStream, "UTF-8");
> Test shows that file doesn't contain UTF-8 characters. Instead saved file contains unicode escapes of non ISO-8859-1 characters.
> This seems wrong, as documentation on setEncoding() method says:
> "Set the encoding used to store the configuration file".
> PropertiesConfiguration.setEncoding() method currently seems to affect only loading the configuration.
> I added one test method that shows that even java.util.Properties class saves the same property value without any problems using utf-8 characters (not unicode escapes that it ) when using smth like that:
> props.store(new OutputStreamWriter(fos, "UTF-8"));
> It looks like a bug to me, or did i misunderstood smth?

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira