Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Message-ID: <1390787797.1228754205618.JavaMail.jira@brutus>
Date: Mon, 8 Dec 2008 08:36:45 -0800 (PST)
From: "Kathey Marsden (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Subject: [jira] Assigned: (DERBY-2161) MessageBuilder can write the
 properties file using the wrong encoding.
In-Reply-To: <31865788.1165506381003.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Kathey Marsden reassigned DERBY-2161:
-------------------------------------

    Assignee:     (was: Andrew McIntyre)

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