Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:19214 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 77907 invoked by uid 1010); 27 Sep 2005 18:37:57 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 77892 invoked from network); 27 Sep 2005 18:37:57 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 27 Sep 2005 18:37:57 -0000 X-Host-Fingerprint: 194.73.73.211 c2bthomr03.btconnect.com FreeBSD 4.7-5.2 (or MacOS X 10.2-10.3) (2) Received: from ([194.73.73.211:26249] helo=c2bthomr03.btconnect.com) by pb1.pair.com (ecelerity 2.0 beta r(6323M)) with SMTP id 14/3C-54476-58199334 for ; Tue, 27 Sep 2005 14:37:57 -0400 Received: from [10.0.0.9] (host81-138-11-136.in-addr.btopenworld.com [81.138.11.136]) by c2bthomr03.btconnect.com (MOS 3.5.9-GR) with ESMTP id CXN75434; Tue, 27 Sep 2005 19:37:10 +0100 (BST) Message-ID: <4339917B.7030304@lsces.co.uk> Date: Tue, 27 Sep 2005 19:37:47 +0100 Organization: L.S.Caine Electronic Services User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.8) Gecko/20050511 X-Accept-Language: en, en-us MIME-Version: 1.0 To: Derick Rethans CC: internals@lists.php.net References: <43393A43.4070805@lsces.co.uk> <43397E48.7080107@lsces.co.uk> In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] timezones & date() breakage From: lester@lsces.co.uk (Lester Caine) Derick Rethans wrote: > gmdate() is for that, date() should always show a local time. The new Local to who ;) > code (which is unfortunately not enabled), allows you do do all kinds of > timezone manipulation. Feel free to test it by setting your CFLAGS to > -DEXPERIMENTAL_DATE_SUPPORT and use the new functions following the > examples from the presentation. I am building a calendar that requires the correct daylight saving entries historically and ongoing. Will the new system support this or is it purely designed to provide the current daylight saving setting - which most sources I've tried to access seem to be limited to? Providing a correct ongoing clock is one thing, but does not address the real problem with timezones and daylight saving. When did they start, what calendar do they follow, which setting do I use for - say - 2000 ? Fortunately I have already stripped the date()/time() raw entries from bitweaver and it uses getUTCTime() which means that only one routine needs managing. Then the display routine works off the CLIENT selection of time/daylight saving ;) I just have not been able to correct the display of the CLIENT selection for the calendar yet :( -- Lester Caine ----------------------------- L.S.Caine Electronic Services Treasurer - Firebird Foundation Inc.