DateTime.parse error on win32 (long timezone names)

ruby-talk
1

This is a well known bug. Please see
Dealing with TZ parsing (on Windows) - Testing 1,2,3... — LiveJournal for the easiest way to "fix"
this (and other details).

Regards,

Dan

This communication is the property of Qwest and may contain confidential or
privileged information. Unauthorized use of this communication is strictly
prohibited and may be unlawful. If you have received this communication
in error, please immediately notify the sender by reply e-mail and destroy
all copies of the communication and any attachments.

···

-----Original Message-----
From: list-bounce@example.com
[mailto:list-bounce@example.com] On Behalf Of Will Rogers
Sent: Wednesday, July 05, 2006 12:47 PM
To: ruby-talk ML
Subject: DateTime.parse error on win32 (long timezone names)

NOTE: this is a cross-post from comp.lang.ruby, because I don't think
anyone read that message, which I posted about two months ago.

The date parsing code in the Ruby stdlib (date/format.rb)
does not parse
strings with long timezones, e.g. "Eastern Daylight Time", as
opposed to
the abbreviated "EDT". On win32, Time#to_s produces a string
with the
long timezone name. So, Time.parse(Time.now.to_s) assumes
the current
year, and DateTime.parse(Time.now.to_s) throws an error.

This is a critical issue for me because it is causing crashes in a
production Rails application during XML serialization in
ActionWebService.