Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:67555 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 25242 invoked from network); 27 May 2013 09:10:20 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 27 May 2013 09:10:20 -0000 Authentication-Results: pb1.pair.com smtp.mail=leafnode@gmail.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=leafnode@gmail.com; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.214.44 as permitted sender) X-PHP-List-Original-Sender: leafnode@gmail.com X-Host-Fingerprint: 209.85.214.44 mail-bk0-f44.google.com Received: from [209.85.214.44] ([209.85.214.44:55336] helo=mail-bk0-f44.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id ED/12-32733-BF223A15 for ; Mon, 27 May 2013 05:10:20 -0400 Received: by mail-bk0-f44.google.com with SMTP id jc3so3523130bkc.3 for ; Mon, 27 May 2013 02:10:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=yLbPQv+7g+AcBQlehu7aST2lUS5h7lGVFB5XPESZGrk=; b=CkSRtayZRUc67ugjcPrGu79jBCDt01Nhk0othd/i0eLNDduIXXf1mNmIs+6VizKPe4 snQj0/snH2dovy1RdCfTF91FDogFqgwzh5Bj7jQNAe2QhuRjDfJ/KkIVN04jyUV/msIr YnWBx/hFQhAef1P/8e6RbhsZjovejVkLno8sEXlhEq0fnDX7rvbJ9zT1a2Bakb7nq+e/ a0pbQWIcuHm5l2HWVaHaT5ErV0ubeNUlmcCzWP10lnJhQeW/eZwZkqNBbDc9erdkmN0v L4iPf415nSSY+ar84vjM2OmoxC6phFkg5IAEgrY2UlzeTy4woqWwXHuagdZZni9pIzaK iusQ== X-Received: by 10.204.191.141 with SMTP id dm13mr790252bkb.106.1369645817353; Mon, 27 May 2013 02:10:17 -0700 (PDT) Received: from [10.0.20.40] (81-18-213-39.static.chello.pl. [81.18.213.39]) by mx.google.com with ESMTPSA id da16sm7963961bkb.2.2013.05.27.02.10.16 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 27 May 2013 02:10:16 -0700 (PDT) Message-ID: <51A322EE.3030706@gmail.com> Date: Mon, 27 May 2013 11:10:06 +0200 User-Agent: Mozilla/5.0 (Windows NT 6.2; WOW64; rv:17.0) Gecko/20130509 Thunderbird/17.0.6 MIME-Version: 1.0 To: internals@lists.php.net References: <51A092FC.4010700@wikimedia.org> <51A1AF3E.5000704@sugarcrm.com> <51A2D395.5030302@sugarcrm.com> <1022965181.20130527011024@cypressintegrated.com> <51A2FD10.7030906@gmail.com> <293168642.20130527032001@cypressintegrated.com> <6c6c2a5a-8762-48fc-9a71-0e9c5dca82a5.maildroid@localhost> <1331934391.20130527050005@cypressintegrated.com> In-Reply-To: <1331934391.20130527050005@cypressintegrated.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] date.timezone E_WARNING -- Really necessary? What's the rationale? From: leafnode@gmail.com (=?UTF-8?B?TGVzemVrIEtydXBpxYRza2k=?=) On 2013-05-27 11:00, Sanford Whiteman wrote: > I'm not talking about storage time zone; we use UTC for that. I'm > talking about the default display time zone. Don't you think that using proper calculations for displaying dates are application developers' responsibility? Whether is it setting a proper TZ in app config, or asking user if it's a better scenario for given app. > Unless we are > misunderstanding each other (not unlikely given how this thread has > sprawled) you seem to be saying the display time zone should be UTC by > default and changed only based on end-user input. I think there are > five legitimate levels of consideration (storage tz, sitewide display > tz, domain/corporate display tz, stored user profile tz, and transient > session tz). That's a very valid point. In my opinion, time should be stored and processed in UTF, and only displayed with a proper offset, but, per what I wrote above, I think it's an app's responsibility to display it properly. --Leszek