Wrong Date Presented about stamp HOT 7 CLOSED

That's because '12' is used to disambiguate month values -- 12 is a tough one because it could be a valid month, day, or year. In this case it might make sense to infer that it's a day because it follows a month... will have to think about this.

In the meantime, I recommend using "Thu, Oct 31, 1988" as your example, because 31 is an obvious day value.

from stamp.

I've got a fix in the meantime, so no rush on my account. I figured you'd like to know about this edge case, though. It is a tough one, since your gem has to do some "interpretation" of what's passed into it. One possible strategy is to throw an error whenever stamp reads a date format that it finds ambiguous instead of stamp making a judgment call.

from stamp.

I've got a similar issue (and a workaround). I'm not sure what's special about the 22nd...

t = Time.now
=> 2012-10-30 15:33:20 +1000
t.stamp("22 October 2012")
=> "10 October 2012" # ooops
t.stamp("28 October 2012")
=> "30 October 2012"

from stamp.

@techiferous @ghiculescu Please update to 0.3.0 and let me know how it looks. I changed the way 2-digit values are disambiguated, which I think will avoid a lot of problems.

from stamp.

That's heaps better. Thanks very much for the prompt response!

from stamp.

@ghiculescu Awesome!

from stamp.

@jeremyw Thanks for fixing this. Sorry it's taken me so long to get back to you; I've been really swamped.

My previous fix was to remove the stamp gem in favor of strftime, which was guaranteed to be correct, since it was producing a bug in the app I was working on that I needed to fix immediately.

I trust that this fix works but I'm so swamped that I'm not going to take the time to re-install the stamp gem on my client's app. So sorry that I can't give you feedback on whether this works for me.

from stamp.