# Re: parsedate doesn't work on Time.now.to\_s

**URL:** <https://www.ruby-forum.com/t/re-parsedate-doesnt-work-on-time-now-to-s/94418>\
**Category:** Ruby\
**Created:** [May 3, 2006, 7:01pm UTC](https://www.ruby-forum.com/t/re-parsedate-doesnt-work-on-time-now-to-s/94418 "2006-05-03T19:01:38Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![BergerS\_Daniel](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/b/bc8723/32.png) [@BergerS\_Daniel](https://www.ruby-forum.com/u/BergerS_Daniel)\
**Post date:** [May 3, 2006, 7:01pm UTC](https://www.ruby-forum.com/t/re-parsedate-doesnt-work-on-time-now-to-s/94418/1 "2006-05-03T19:01:38Z")

</div>

> ParseDate.parsedate(Time.now.to\_s)  
> =\> [nil, 5, 2, 20, 17, 57, “GMT”, 2]
> 
> It seems that parsedate is not able to detect the year from  
> the standard  
> string conversion of a date/time. Is there another way to do  
> this? Is it  
> the same in the US as for me here in the UK? It seems rather  
> inconsistent.
> 
> Julian

It’s not an issue specific to the UK:

irb(main):003:0\> Time.now.to\_s  
=\> “Tue May 02 13:46:27 Mountain Daylight Time 2006”  
irb(main):043:0\> ParseDate.parsedate(Time.now.to\_s)  
=\> [nil, 5, 2, 13, 46, 18, “Mountain”, 2]

The problem is that ParseDate does not handle long time zone  
names, only abbreviated forms. Consider:

irb(main):006:0\> time = “Tue May 02 13:46:27 MST 2006”  
=\> “Tue May 02 13:46:27 MST 2006”  
irb(main):007:0\> ParseDate.parsedate(time)  
=\> [2006, 5, 2, 13, 46, 27, “MST”, 2]

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.