Rails Ruby on Rails → 2.x

Comments and changes to this ticket

• 

  Geoff Buesing November 13th, 2008 @ 02:35 PM

  • State changed from “new” to “invalid”
  • Tag set to “activesupport, patch, timezone”

  According to the latest version of TZInfo, the non-dst utc offset for Buenos Aires was -10800 (i.e., -03:00) in 2008, and will be the same in 2009.

  Please reopen if I'm missing something here.

• 

  Emilio Tagua November 13th, 2008 @ 02:42 PM

  If you select Buenos Aires as timezone right now, the offset used is -7200, i had to monkey patch this on my apps to show the valid offset when returning tz 'Buenos Aires'.

  The offset has been changed a couple of weeks ago and as i said it will be -0200 until March 2009.

  Check this out:

  
  >> Time.now.in_time_zone 'Buenos Aires'
  => Thu, 13 Nov 2008 12:40:48 ARST -02:00
  

• 

  Geoff Buesing November 13th, 2008 @ 03:15 PM

  That's because Buenos Aires is observing daylight savings time:

  
  >> Time.zone = 'Buenos Aires'
  => "Buenos Aires"
  >> Time.zone.now
  => Thu, 13 Nov 2008 13:08:59 ARST -02:00
  >> Time.zone.now.dst?
  => true
  >> t2 = Time.zone.now + 6.months
  => Wed, 13 May 2009 13:09:20 ART -03:00
  >> t2.dst?
  => false
  

  The #utc_offset of a TimeZone is fixed to the non-dst offset, so that it will appear consistently in the time zone select menu.

  For example: US Central time will always appear in the time zone select as:

  "(GMT-06:00) Central Time (US & Canada)"

  whether or not it's currently dst.