Return-Path: 
 <derby-dev-return-285-apmail-db-derby-dev-archive=db.apache.org@db.apache.org>
Delivered-To: apmail-db-derby-dev-archive@www.apache.org
Received: (qmail 45998 invoked from network); 9 Sep 2004 22:52:51 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199)
  by minotaur-2.apache.org with SMTP; 9 Sep 2004 22:52:51 -0000
Received: (qmail 59929 invoked by uid 500); 9 Sep 2004 22:52:50 -0000
Delivered-To: apmail-db-derby-dev-archive@db.apache.org
Received: (qmail 59836 invoked by uid 500); 9 Sep 2004 22:52:50 -0000
Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
list-help: <mailto:derby-dev-help@db.apache.org>
list-unsubscribe: <mailto:derby-dev-unsubscribe@db.apache.org>
list-post: <mailto:derby-dev@db.apache.org>
List-Id: "Derby Development" <derby-dev@db.apache.org>
Reply-To: "Derby Development" <derby-dev@db.apache.org>
Delivered-To: mailing list derby-dev@db.apache.org
Received: (qmail 59822 invoked by uid 99); 9 Sep 2004 22:52:49 -0000
X-ASF-Spam-Status: No, hits=0.1 required=10.0
	tests=DNS_FROM_RFC_ABUSE
X-Spam-Check-By: apache.org
Received-SPF: neutral (hermes.apache.org: local policy)
Received: from [206.190.39.154] (HELO web52703.mail.yahoo.com)
 (206.190.39.154)
  by apache.org (qpsmtpd/0.28) with SMTP; Thu, 09 Sep 2004 15:52:47 -0700
Message-ID: <20040909225244.66612.qmail@web52703.mail.yahoo.com>
Received: from [200.164.169.138] by web52703.mail.yahoo.com via HTTP;
 Thu, 09 Sep 2004 19:52:44 ART
Date: Thu, 9 Sep 2004 19:52:44 -0300 (ART)
From: =?iso-8859-1?q?Halley=20Pacheco=20de=20Oliveira?=
 <halleypo@yahoo.com.br>
Subject: Re: Derby messages localization
To: Derby Development <derby-dev@db.apache.org>
In-Reply-To: <61F14D25-01F0-11D9-9789-003065CBB010@nonintuitive.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
X-Virus-Checked: Checked
X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N

Dear Andrew,

Thank you very much for your help. I changed the file
${derby.source}/build.xml as shown bellow:

568a569
>org/apache/derby/loc/sysinfoMessages_pt_BR.properties,
569a571
>org/apache/derby/loc/toolsmessages_pt_BR.properties,
662a665
>org/apache/derby/loc/sysinfoMessages_pt_BR.properties,
663a667
>org/apache/derby/loc/toolsmessages_pt_BR.properties,

and the file
${derby.source}/java/tools/org/apache/derby/loc/build.xml
as show bellow:

21a22
><include name="sysinfoMessages_pt_BR.properties"/>
22a24
><include name="toolsmessages_pt_BR.properties"/>

and translated a line in
toolsmessages_pt_BR.properties to test. It is working
fine. When I finish the translation I will contribute
with the files.

Halley

 --- Andrew McIntyre <fuzzylogic@nonintuitive.com>
escreveu: 
> 
> On Sep 8, 2004, at 5:32 AM, Halley Pacheco de
> Oliveira wrote:
> 
> > What is wrong ? I couldn't find the
> csLocale_pt_BR.jar
> > file. Is that the problem ?
> 
> IBM did not contribute the translated message files
> for Derby. It is my 
> understanding that they are looking into doing this,
> but there are no 
> definite plans for when or how that will happen.
> There will be 
> translated messages in the Cloudscape 10.0
> commercial release.
> 
> That said, feel free to translate the messages and
> contribute them to 
> Derby. For toolsmessages, you should create a new
> file, 
> toolsmessages_pt_BR.properties  in
> java/tools/org/apache/derby/loc and 
> put the translated messages there. You will then
> need to update the 
> build.xml in that directory so that the messages are
> copied over to 
> ${out.dir}/org/apache/derby/loc. This should make
> the translated 
> messages available to the tools.
> 
> If you would like sysinfo to display that support
> for your locale is 
> present, you will need to generate an info file for
> your locale. See 
> Main.reportLocales() in
> java/tools/org/apache/derby/impl/tools/sysinfo 
> (lines 326-413) to see how locale support
> information is reported. 
> Sysinfo determines presence of support for a
> particular locale not from 
> the presence of message files, but from the presence
> of a locale info 
> properties file,
> org.apache.derby.info.locale_{locale}.properties.
> This 
> file should contain proper values for the
> derby.locale.* properties 
> that reportLocales() tries to look up:
> 
> derby.locale.external.name, with the form 'Locale
> Name [ISO_code]' e.g.:
> derby.locale.external.name= Portuguese/Brazilian
> [pt_BR]
> 
> The following properties correspond to the
> properties in 
> org.apache.derby.loc.DBMS.properties:
> derby.locale.version.major
> derby.locale.version.minor
> derby.locale.version.maint
> derby.locale.build.number
> 
> The values of these properties are passed to 
>
org.apache.derby.iapi.services.info.ProductVersionHolder
> and sysinfo 
> then reports the version via that classes'
> fullVersionString() method.
> 
> As a side note, better locale support (from a
> build/tools perspective) 
> would be a good thing to put on Derby's to-do list.
> 
> andrew
> 
>  



	
	
		
_______________________________________________________
Yahoo! Acesso Gr�tis - navegue de gra�a com conex�o de qualidade! 
http://br.acesso.yahoo.com/