From e2d7f42498f9cb8cb4b0f4ddd7fcd395829157f2 Mon Sep 17 00:00:00 2001 From: Shantonu Sen Date: Wed, 6 Sep 2000 22:48:43 +0000 Subject: [PATCH] Included changes to dtimep.lex to remove military zone parsing. --- ChangeLog | 14 ++++++++++++++ 1 file changed, 14 insertions(+) diff --git a/ChangeLog b/ChangeLog index 2ba743e..824f2a7 100644 --- a/ChangeLog +++ b/ChangeLog @@ -1,3 +1,17 @@ +Wed Sep 6 22:40:03 2000 Shantonu Sen + + * Tracked down the problem in the new dtimep where time + zones were being radically misreported. It was because the + parser knew about military time zones (such as M or E) but in + some cases did not know about the textual representation of + some zones (like MET). When it encountered one of these, the + date parser misread MET as the military time zone T (well, first + zone M, then E, and finally T). I took military zones out, and + things seem much better. Also, the default behavior of parsing + time zones appears to default to GMT in the absence of better + info, which is less bogus than assuming the mail came from the + current time zone, which was the behavior in 1.04. + Thu Aug 10 13:22:13 2000 Dan Harkless * Decided that limiting the message number columns to 3 on my -- 1.7.10.4