Date: Thu, 13 Apr 2000 11:25:52 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: djgpp AT delorie DOT com
Subject: Re: timezone problems: tm_isdst not set; strftime("%z") is -0000
In-Reply-To: <38f4e8db.19823033@news.freeserve.net>
Message-ID: <Pine.SUN.3.91.1000413112455.28180D-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: djgpp AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk


On Wed, 12 Apr 2000, Steamer wrote:

> I've just tried using cst6cdt and I do get the correct things:
> 
>   tm_isdst    = 1 (** should be 1 **)
>   __tm_zone   = CDT (** should be CDT **)
>   __tm_gmtoff = -18000 (** should be -18000 **)
> 
> I'm using DJGPP 2.03, but the my zoneinfo files are from 2.02.
> 
> I don't know how to explain this (unless the cst6cdt file in 2.03 is corrupt),

Yes, it seems like the timezone files in v2.03 are wrong.  (We don't
create those files, we import them from some publicly-available data
base, see section 22.20 of the FAQ for details).

Thanks for looking into this.

> but maybe it will help convince Eli that something really is going wrong
> somewhere.

I didn't say I didn't believe the original report.  I asked for a specific 
test case precisely *because* I wanted to look into this.  Thanks for 
providing valuable input for my inquiries.