db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew McIntyre (JIRA)" <j...@apache.org>
Subject [jira] Updated: (DERBY-2161) MessageBuilder can write the properties file using the wrong encoding.
Date Thu, 31 May 2007 08:02:15 GMT

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

Andrew McIntyre updated DERBY-2161:
-----------------------------------

    Fix Version/s:     (was: 10.3.0.0)

Setting fix version to Unknown. Fixing this issue is not a requirement for any future release.
Need to determine the proper behavior for MessageBuilder when processing newilnes in message
files.



> 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.0.0
>            Reporter: Daniel John Debrunner
>            Assignee: Andrew McIntyre
>         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.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message