From dev-return-34928-apmail-directory-dev-archive=directory.apache.org@directory.apache.org Sun Sep 05 08:24:07 2010 Return-Path: Delivered-To: apmail-directory-dev-archive@www.apache.org Received: (qmail 89896 invoked from network); 5 Sep 2010 08:24:06 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 5 Sep 2010 08:24:06 -0000 Received: (qmail 38916 invoked by uid 500); 5 Sep 2010 08:24:06 -0000 Delivered-To: apmail-directory-dev-archive@directory.apache.org Received: (qmail 38712 invoked by uid 500); 5 Sep 2010 08:24:04 -0000 Mailing-List: contact dev-help@directory.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Apache Directory Developers List" Delivered-To: mailing list dev@directory.apache.org Received: (qmail 38700 invoked by uid 99); 5 Sep 2010 08:24:03 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 05 Sep 2010 08:24:03 +0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests=FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of ayyagarikiran@gmail.com designates 74.125.82.178 as permitted sender) Received: from [74.125.82.178] (HELO mail-wy0-f178.google.com) (74.125.82.178) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 05 Sep 2010 08:23:56 +0000 Received: by wyb42 with SMTP id 42so4144193wyb.37 for ; Sun, 05 Sep 2010 01:23:35 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:sender:received :in-reply-to:references:date:x-google-sender-auth:message-id:subject :from:to:content-type:content-transfer-encoding; bh=6bvWtqOFAEdYuGtypAA7br2GxMCxA8YK89oP/xek/co=; b=qKyaJpaN/a+3pHwBVcvpaNdgRjVJME7F1nG1e6OXB/uRV79MEsuMYFwevAI0xYOotD uYsBkJ2JEphWk23YVR0hEay3eKslPVIRTsQe3W8ykI2OVhmJng4OhpnM6uswLjXJ12Gw p1q9uF8qCTJ2O3xvuBERpu7TFBoCiYqbtJ7kc= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type :content-transfer-encoding; b=dR/ZFuwvjI9hUtycHIRC2zwApFB/ZoAyi1JPxIYIN58H3OQvd0gRIg4bAMwEP6VZX4 wVS/V/Kjk0ITQX0x/YNJ5Adm5pEqZ4OAM/k1arVH7SK9eMDn1302GZa9atOrnMgfJX5E uDH2bZppQzFOzUZY0ZeyN6AQAfp39loEblOiw= MIME-Version: 1.0 Received: by 10.216.185.72 with SMTP id t50mr2513720wem.77.1283675015558; Sun, 05 Sep 2010 01:23:35 -0700 (PDT) Sender: ayyagarikiran@gmail.com Received: by 10.216.59.148 with HTTP; Sun, 5 Sep 2010 01:23:35 -0700 (PDT) In-Reply-To: <4C835370.2000207@gmail.com> References: <4C835370.2000207@gmail.com> Date: Sun, 5 Sep 2010 13:53:35 +0530 X-Google-Sender-Auth: N2uOBiGzzBy9ADMt3WpfsUuB4Is Message-ID: Subject: Re: I18n for debug messages ? From: Kiran Ayyagari To: Apache Directory Developers List , elecharny@apache.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable On Sun, Sep 5, 2010 at 1:53 PM, Emmanuel Lecharny wro= te: > =A0Hi guys, > > I'm not sure it's worthy to move DEBUG level messages to i18n. To me, FAT= AL, > 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 Kiran Ayyagari