Mailing-List: contact dev-help@tomcat.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Developers List" <dev@tomcat.apache.org>
Received-SPF: pass (nike.apache.org: domain of knst.kolinko@gmail.com
 designates 209.85.220.175 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:sender:date:x-google-sender-auth:message-id:subject
         :from:to:content-type:content-transfer-encoding;
        b=RkV/mGAkB8f6yaZTcrUpTR+RS/hgcg1cXazquMLU1Tax95ruLmXXDyBIlKTDiQqP9J
         UkmVAZofnLNv6/soqJZQWd5NvjLA8N8Rro85IsbJ5rPy/Ql4feSNUCrMaes1GNqCnhBT
         6XNeN4EgYun/rrjnyCOij7goi5GKoRC7foxJs=
MIME-Version: 1.0
Sender: knst.kolinko@gmail.com
Date: Fri, 22 May 2009 04:35:44 +0400
Message-ID: <427155180905211735p20634b2am88725c06cc79344c@mail.gmail.com>
Subject: Coding Guidelines, encodings, keywords
From: Konstantin Kolinko <kkolinko@apache.org>
To: Tomcat Developers List <dev@tomcat.apache.org>
Content-Type: text/plain; charset=KOI8-R
Content-Transfer-Encoding: quoted-printable

Hi, all!

Are there any Coding Guidelines that we ought to follow,
or is our project on our own there?

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 encodi=
ng.

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 nam=
es.

E.g.:
$Revision: 776947 $ $Date: 2009-05-21 08:33:21 +0400 (=FE=D4, 21 =CD=C1=CA =
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