Mailing-List: contact dev-help@directory.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Apache Directory Developers List" <dev@directory.apache.org>
Message-ID: <4C83595B.6040503@apache.org>
Date: Sun, 05 Sep 2010 10:48:27 +0200
From: =?ISO-8859-1?Q?Emmanuel_L=E9charny?= <elecharny@apache.org>
Reply-To: elecharny@apache.org
Organization: The Apache Software Foundation
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US;
 rv:1.9.2.8) Gecko/20100802 Thunderbird/3.1.2
MIME-Version: 1.0
To: Apache Directory Developers List <dev@directory.apache.org>
Subject: Re: I18n for debug messages ?
References: <4C835370.2000207@gmail.com>
 <AANLkTi=pFB=TWob2v2q95T_WAG7RBNVQ5GnPhuiimMqv@mail.gmail.com>
 <4C835679.8010802@symas.com>
In-Reply-To: <4C835679.8010802@symas.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit

  On 9/5/10 10:36 AM, Howard Chu wrote:
> Kiran Ayyagari wrote:
>> On Sun, Sep 5, 2010 at 1:53 PM, Emmanuel 
>> Lecharny<elecharny@gmail.com>  wrote:
>>>   Hi guys,
>>>
>>> I'm not sure it's worthy to move DEBUG level messages to i18n. To 
>>> me, FATAL,
>>> ERROR, INFO and WARNING should be i18ned, but DEBUG messages are 
>>> more an
>>> indication for high level developpers who will have a clue about what's
>>> going on in the server, mainly us, in fact.
>> +1, let us keep DEBUG messages without i18n, having them in plain text
>> in the code improves
>>    readability during debugging
>
> It's a real pain to grep or google for error messages if you have to 
> cover multiple languages in your search...
sure enough. Hopefully, all our messages have a code, like ERR_XXXX, so 
whatever language the user has, it should be easy to get a clue about 
what's going on. (assuming we don't modify the number from version X to 
version Y of course !)

(I should check we add this ERR_XXXXX number in front of messages...)


-- 
Regards,
Cordialement,
Emmanuel L�charny
www.iktek.com