You are viewing a plain text version of this content. The canonical link for it is here.

Posted to derby-dev@db.apache.org by "Rick Hillegas (JIRA)" <ji...@apache.org> on 2013/06/20 21:34:20 UTC

[jira] [Updated] (DERBY-2161) MessageBuilder can write the properties file using the wrong encoding.

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

Rick Hillegas updated DERBY-2161:
---------------------------------

    Urgency: Normal
     Labels: derby_triage10_11  (was: )
    
> MessageBuilder can write the properties file using the wrong encoding.
> ----------------------------------------------------------------------
>
>                 Key: DERBY-2161
>                 URL: https://issues.apache.org/jira/browse/DERBY-2161
>             Project: Derby
>          Issue Type: Bug
>          Components: Build tools
>    Affects Versions: 10.3.1.4
>            Reporter: Daniel John Debrunner
>              Labels: derby_triage10_11
>         Attachments: derby-2161-v1.diff
>
>
> MessageBuilder  uses java.io.FileWriter to write the properties files which picks up the default encoding, but properties files have a defined encoding ISO 8859-1 with unicode esacape sequences. I don't see anything in the build.xml that forces the encoding or  when running the task. Also I don't see any code that implements Unicode escapes.
> I think a better approach would be to use the Properties class to write the properties file, then we don't have to try and maintain the same logic for formatting the output file.

--
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