Return-Path: Delivered-To: apmail-tomcat-dev-archive@www.apache.org Received: (qmail 13276 invoked from network); 22 May 2009 01:06:33 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 22 May 2009 01:06:33 -0000 Received: (qmail 99190 invoked by uid 500); 22 May 2009 01:06:45 -0000 Delivered-To: apmail-tomcat-dev-archive@tomcat.apache.org Received: (qmail 99123 invoked by uid 500); 22 May 2009 01:06:45 -0000 Mailing-List: contact dev-help@tomcat.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Tomcat Developers List" Delivered-To: mailing list dev@tomcat.apache.org Received: (qmail 99112 invoked by uid 99); 22 May 2009 01:06:45 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 22 May 2009 01:06:45 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: local policy) Received: from [72.22.94.67] (HELO virtual.halosg.com) (72.22.94.67) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 22 May 2009 01:06:33 +0000 Received: (qmail 3483 invoked from network); 21 May 2009 20:06:12 -0500 Received: from 38-171-19-72.skybeam.com (HELO ?192.168.1.42?) (72.19.171.38) by halosg.com with (DHE-RSA-AES256-SHA encrypted) SMTP; 21 May 2009 20:06:12 -0500 Message-ID: <4A15FA80.10406@hanik.com> Date: Thu, 21 May 2009 19:06:08 -0600 From: Filip Hanik - Dev Lists User-Agent: Thunderbird 2.0.0.21 (X11/20090320) MIME-Version: 1.0 To: Tomcat Developers List Subject: Re: Coding Guidelines, encodings, keywords References: <427155180905211735p20634b2am88725c06cc79344c@mail.gmail.com> In-Reply-To: <427155180905211735p20634b2am88725c06cc79344c@mail.gmail.com> Content-Type: text/plain; charset=KOI8-R; format=flowed Content-Transfer-Encoding: 8bit X-Virus-Checked: Checked by ClamAV on apache.org Konstantin Kolinko wrote: > Hi, all! > > Are there any Coding Guidelines that we ought to follow, > or is our project on our own there? > spaces instead of tabs :) > I am interested in clarifying the following question: > What is the character encoding for our sources. > > Our build scripts do not specify an explicit encoding yet, > and, as I heard, some months ago the build environment for our releases > changed from some western Windows to Linux with a locale using UTF-8 encoding. > > I would like to draw your attention that there is such SVN keyword as $Date$, > that expands to UTF-8 string containing localized month and day of week names. > > E.g.: > $Revision: 776947 $ $Date: 2009-05-21 08:33:21 +0400 (��, 21 ��� 2009) $ > > That makes the files that use that keyword de-facto UTF-8 on > non-English locales. > > More on svn keywords: > http://svnbook.red-bean.com/nightly/en/svn.advanced.props.special.keywords.html > > A workaround would be to either limit the string width (e.g. $Date:: > 2009-05-21 08:33:21 #$) > or to use $Id$ instead. > > Do we officially acknowledge that the sources are UTF-8? > > What explicit encoding should be specified in javac and javadoc tasks > in our build files? > ISO-8859-1 or UTF-8 ? > > > Best regards, > Konstantin Kolinko > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org > For additional commands, e-mail: dev-help@tomcat.apache.org > > > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org For additional commands, e-mail: dev-help@tomcat.apache.org