Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:19228
Return-Path: <derick@php.net>
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Delivered-To: mailing list internals@lists.php.net
Received: (qmail 79212 invoked by uid 1010); 28 Sep 2005 07:37:02 -0000
Delivered-To: ezmlm-scan-internals@lists.php.net
Delivered-To: ezmlm-internals@lists.php.net
Received: (qmail 79197 invoked from network); 28 Sep 2005 07:37:02 -0000
Received: from unknown (HELO lists.php.net) (127.0.0.1)
  by localhost with SMTP; 28 Sep 2005 07:37:02 -0000
X-Host-Fingerprint: 82.94.239.5 jdi.jdi-ict.nl Linux 2.5 (sometimes 2.4) (4)
Received: from ([82.94.239.5:51987] helo=jdi.jdi-ict.nl)
	by pb1.pair.com (ecelerity 2.0 beta r(6323M)) with SMTP
	id 38/8C-54476-D184A334 for <internals@lists.php.net>; Wed, 28 Sep 2005 03:37:02 -0400
Received: from localhost (localhost [127.0.0.1])
	by jdi.jdi-ict.nl (8.12.11/8.12.11) with ESMTP id j8S7ax3v032006;
	Wed, 28 Sep 2005 09:36:59 +0200
Received: from localhost (localhost [127.0.0.1])
	by jdi.jdi-ict.nl (8.12.11/8.12.11) with ESMTP id j8S7asfS031983;
	Wed, 28 Sep 2005 09:36:54 +0200
Date: Wed, 28 Sep 2005 09:36:53 +0200 (CEST)
X-X-Sender: derick@localhost
To: Lester Caine <lester@lsces.co.uk>
cc: internals@lists.php.net
In-Reply-To: <433998B1.60106@lsces.co.uk>
Message-ID: <Pine.LNX.4.62.0509280936130.24804@localhost>
References: <Pine.LNX.4.62.0509271328530.27768@shire.zend.office>
	<Pine.LNX.4.62.0509271323290.24804@localhost> <Pine.LNX.4.62.0509271436440.28004@shire.zend.office>
	<Pine.LNX.4.62.0509271349291.24804@localhost> <43393A43.4070805@lsces.co.uk>
	<Pine.LNX.4.62.0509271435480.24804@localhost> <43397E48.7080107@lsces.co.uk>
	<Pine.LNX.4.62.0509271943360.24804@localhost> <4339917B.7030304@lsces.co.uk>
	<Pine.LNX.4.62.0509272041520.24804@localhost> <433998B1.60106@lsces.co.uk>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Virus-Scanned: by amavisd-new at jdi-ict.nl
Subject: Re: [PHP-DEV] timezones & date() breakage
From: derick@php.net (Derick Rethans)

On Tue, 27 Sep 2005, Lester Caine wrote:

> Derick Rethans wrote:
> 
> > >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?
> > 
> > It should do it for historical data too, but that data might not always be
> > available - the database that I'm using does have a lot of information
> > though.
> I've got some things to check against ;)
> Not sure I spotted your source of data?

timezone_transistions_get() in the new date/time support code.

Derick