Still getting the same INVALID_TIMEZONE error today using numerical offsets (haven't tried "zzzz" specifier yet). I thought the fix would be rolled out by now (currently using v201008). When will it be fixed?
On Dec 5, 9:32 am, David Torres <davi...@google.com> wrote: > Hi Brian, > > The fix should be rolling out today so you can start using GMT-offset type > of timezone formats tomorrow, in the meantime if you use (and I'm assuming > you are using Java) a "zzzz" specifier should give you the timezone in > letters as "Eastern Standard Time" but only if it knows the locale on which > the date is on. > > Best, > > -David Torres - AdWords API Team -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ Also find us on our blog and discussion group: http://adwordsapi.blogspot.com http://groups.google.com/group/adwords-api =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ You received this message because you are subscribed to the Google Groups "AdWords API Forum" group. To post to this group, send email to adwords-api@googlegroups.com To unsubscribe from this group, send email to adwords-api+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/adwords-api?hl=en
