Return-Path: Delivered-To: apmail-directory-dev-archive@www.apache.org Received: (qmail 34391 invoked from network); 17 Mar 2010 12:50:38 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 17 Mar 2010 12:50:38 -0000 Received: (qmail 52861 invoked by uid 500); 17 Mar 2010 12:50:37 -0000 Delivered-To: apmail-directory-dev-archive@directory.apache.org Received: (qmail 52788 invoked by uid 500); 17 Mar 2010 12:50:37 -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 52781 invoked by uid 99); 17 Mar 2010 12:50:37 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 17 Mar 2010 12:50:37 +0000 X-ASF-Spam-Status: No, hits=0.7 required=10.0 tests=RCVD_IN_DNSWL_NONE,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (nike.apache.org: local policy) Received: from [62.179.121.34] (HELO viefep14-int.chello.at) (62.179.121.34) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 17 Mar 2010 12:50:29 +0000 Received: from edge04.upcmail.net ([192.168.13.239]) by viefep14-int.chello.at (InterMail vM.8.01.02.02 201-2260-120-106-20100312) with ESMTP id <20100317125008.HAKZ13262.viefep14-int.chello.at@edge04.upcmail.net> for ; Wed, 17 Mar 2010 13:50:08 +0100 Received: from [192.168.1.50] ([84.74.100.246]) by edge04.upcmail.net with edge id uCq61d06w5JxopQ04Cq8Jv; Wed, 17 Mar 2010 13:50:08 +0100 X-SourceIP: 84.74.100.246 Message-ID: <4BA0CFFE.7030601@apache.org> Date: Wed, 17 Mar 2010 13:50:06 +0100 From: Felix Knecht Reply-To: felixk@apache.org User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.8) Gecko/20100308 Thunderbird/3.0.3 MIME-Version: 1.0 To: Apache Directory Developers List Subject: Re: About I18n References: <4BA0BC09.5070600@gmail.com> In-Reply-To: <4BA0BC09.5070600@gmail.com> X-Enigmail-Version: 1.0.1 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Cloudmark-Analysis: v=1.1 cv=M71sKKeyFebLYdq5hFNIGMR02ATQkL1qNhm49ttUYSY= c=1 sm=0 a=pXoq77xVGrQA:10 a=8nJEP1OIZ-IA:10 a=xe8BsctaAAAA:8 a=dNBi22XSbxpicEoaT9QA:9 a=sGqHbaC6vrr8KogOUzQA:7 a=SHWaLCG63Pb5Tt74inUn3_gAWRwA:4 a=wPNLvfGTeEIA:10 a=iUJUt66l4nvDMppZ:21 a=KHPo2t-TZTSoUTUO:21 a=HpAAvcLHHh0Zw7uRqdWCyQ==:117 X-Virus-Checked: Checked by ClamAV on apache.org -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 > This is just great, but I think we should go a bit further. If we want > to add a new error message, we have to add a new number at the end of > the list. As all the numbers start from 1 and are incremented, it > becomes rapidly difficult to group errors by their numbers (ie, all the > errors between 450 and 460 are related to operation X). For the apacheds this is true, but for the shared I started a new block of numbers for each submodule (01xxx, 02xxx, ...). Maybe a refactoring of the apacheds is needed. > > What about defining a number which would inform immediately about the > kind of message we are dealing with ? We can for instance use hex > numbers, where the two higher bits will be used to indicate the log level : > DEBUG = 00XXXXXXXXX... > INFO = 01XXXXXXXXX... > WARN = 10XXXXXXXXX... > ERROR = 11XXXXXXXXX... ? ATM only errors should be i18n-tyified. This means only ERROR/FATAL may happen. All the other things are not yet translated. Furthermore a log messages indicates clearly of which level it is. Do I miss something? > > The idea is that if the number is <0, then it's an error or a warning. > > IN the same vein, we can also split the errors by family. As the number > will be an integer, it remains 30 bits to store informations. Assuming > that shared messages are indicated by the bit number 29, then we have a > way to split again : > 101xxxxxx = a warning in the shared module > 1111xxxxx = an error in the shared module, asn1 subproject... > > etc. > > wdyt ? > -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.14 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkugz/4ACgkQ2lZVCB08qHFU1wCfXS8Z4S9M5mvNjvBHzrtiQCEQ xkcAnioPrxyxep0Ih2pSc+XKoZ3tg1Lh =qoVr -----END PGP SIGNATURE-----