Return-Path: Delivered-To: apmail-geronimo-dev-archive@www.apache.org Received: (qmail 52182 invoked from network); 11 May 2010 08:28:54 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 11 May 2010 08:28:54 -0000 Received: (qmail 54847 invoked by uid 500); 11 May 2010 08:28:54 -0000 Delivered-To: apmail-geronimo-dev-archive@geronimo.apache.org Received: (qmail 54614 invoked by uid 500); 11 May 2010 08:28:53 -0000 Mailing-List: contact dev-help@geronimo.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: Reply-To: dev@geronimo.apache.org List-Id: Delivered-To: mailing list dev@geronimo.apache.org Received: (qmail 54602 invoked by uid 99); 11 May 2010 08:28:53 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 11 May 2010 08:28:53 +0000 X-ASF-Spam-Status: No, hits=1.2 required=10.0 tests=AWL,FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_NONE,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of xhhsld@gmail.com designates 209.85.221.181 as permitted sender) Received: from [209.85.221.181] (HELO mail-qy0-f181.google.com) (209.85.221.181) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 11 May 2010 08:28:46 +0000 Received: by qyk11 with SMTP id 11so6984529qyk.13 for ; Tue, 11 May 2010 01:28:25 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:content-type; bh=mBd7iccFR36rOeLsc6+WfPHqAE1tx0hl3lYXqHueHdg=; b=D2ckrUZSzaBGdi2XeE/TU6Hl5NoSjyEo1V4SMyxk7cfHBAfmRwLZV3LXr6t/fXD1C/ p/OyngH0NHvVe1GsabHgbNKn5JjTzkyOvFsN84lT9RSCK6Lq+hcPpks0Ze0NE1k3pq2N moH6KgW6UMNwr7TnaLWwqRLI4rqhFpP8WxK8g= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=X9w2JzstCpL8+WP5TZsKRyDAF4JmQYxDUjOrQA/ZUo0C9mrnGFNkowy8p7FQr4I/zE rVv5qH5AopFUDD5fmwynPhE1qNNFaujmoy1UeFe90TgCX0SGi+z3U5hQpNzrgvNdjoZa iQZ/27sv2u0j0ggZEgeGo1y9NG4dcmx/14Gys= MIME-Version: 1.0 Received: by 10.229.213.140 with SMTP id gw12mr4304529qcb.96.1273566505849; Tue, 11 May 2010 01:28:25 -0700 (PDT) Received: by 10.229.189.203 with HTTP; Tue, 11 May 2010 01:28:25 -0700 (PDT) In-Reply-To: References: Date: Tue, 11 May 2010 16:28:25 +0800 Message-ID: Subject: Re: What's the reason that the characters in properties files are in unicode for branch/2.1? From: Ivan To: dev@geronimo.apache.org Content-Type: multipart/alternative; boundary=00163630f4452dd6dc04864d4fa6 --00163630f4452dd6dc04864d4fa6 Content-Type: text/plain; charset=ISO-8859-1 There are some useful Eclipse plugins, like http://sourceforge.net/projects/eclipse-rbe/ 2010/5/11 chi runhua > Thank you for the info, Ivan. > > So any suggestions on how we shall update those messages in 2.1? > > > Jeff > > > On Tue, May 11, 2010 at 4:03 PM, Ivan wrote: > >> The java properties file could only read those characters in unicode form. >> In Geronimo 2.2, to make it easy to edit those property file, we use a mave >> plugin to do the convertion in the building process. >> >> 2010/5/11 chi runhua >> >> Hi devs, >>> >>> I am about to update some Chinese translation of UI description for >>> branche/2.1, but noticed that the Chinese characters in some of .properties >>> files are encoded as Unicode, which makes the update kinda difficult. >>> >>> But in branch/2.2, we don't have the problem. >>> >>> Any idea why we have two sets of file encoding mechanism for non-en >>> characters? >>> >>> Thanks. >>> >>> For example. >>> [1]. >>> https://svn.apache.org/repos/asf/geronimo/server/branches/2.1/plugins/console/plugin-portlets/src/main/resources/pluginportlets_zh.properties >>> [2]. >>> https://svn.apache.org/repos/asf/geronimo/server/branches/2.2/plugins/console/plugin-portlets/src/main/resources/pluginportlets_zh.properties >>> >>> >>> Jeff >>> >> >> >> >> -- >> Ivan >> > > -- Ivan --00163630f4452dd6dc04864d4fa6 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable There are some useful Eclipse plugins, like http://sourceforge.net/projects/eclipse-rbe/<= br>
2010/5/11 chi runhua &l= t;chirunhua@gmail.com>=
Thank you for the= info, Ivan.

So any suggestions on how we shall update t= hose messages in 2.1?


Jeff=A0


On Tue, May 11, 2010 at 4:03 PM, Ivan <= span dir=3D"ltr"><= xhhsld@gmail.com> wrote:
The java properti= es file could only read those characters in unicode form. In Geronimo 2.2, = to make it easy to edit those property file, we use a mave plugin to do the= convertion in the building process.

2010/5/11 chi runhua <chirunhua@gmail.com>
=

Hi devs,

I am about to update some Chinese translation o= f UI description for branche/2.1, but noticed that the Chinese characters i= n some of .properties files are encoded as Unicode, which makes the update = kinda difficult.

But in branch/2.2, we don't have the problem.
=

Any idea why we have two sets of file encoding mechanis= m for non-en characters?

Thanks.

For example.


Jeff



--
Ivan




--
Ivan
--00163630f4452dd6dc04864d4fa6--