[ruby-core:112280] [Ruby master Misc#19096] [Question] Time with `-00:00` offset is in UTC

Issue #19096 has been updated by nobu (Nobuyoshi Nakada).





duerst (Martin D=FCrst) wrote in #note-10:

> I'm not sure whether and how much this is relevant, but please note that =
the Sedate WG in the IETF has a draft (https://www.ietf.org/archive/id/draf=
t-ietf-sedate-datetime-extended-07.html, close to final) that updates RFC 3=
339 (https://www.rfc-editor.org/rfc/rfc3339). For details, please check htt=
ps://www.ietf.org/archive/id/draft-ietf-sedate-datetime-extended-07.html#na=
me-updating-rfc-3339.



Thank you for the interesting information.



Although that draft seems not recommending use of `-00:00`, but it also say=
s=20



> the present specification however does not formally deprecate this syntax.



at https://www.ietf.org/archive/id/draft-ietf-sedate-datetime-extended-07.h=
tml#section-2-6





----------------------------------------

Misc #19096: [Question] Time with `-00:00` offset is in UTC

https://bugs.ruby-lang.org/issues/19096#change-101713



* Author: andrykonchin (Andrew Konchin)

* Status: Closed

* Priority: Normal

----------------------------------------

It's a bit unexpected but



```ruby

Time.new(2022, 1, 1, 0, 0, 0, "-00:00").utc?

# =3D> true

```



But time with `+00:00` or `0` offset is treated as not UTC time:



```ruby

Time.new(2022, 1, 1, 0, 0, 0, "+00:00").utc? # =3D> false

Time.new(2022, 1, 1, 0, 0, 0, 0).utc? # =3D> false

```



Is it an intentional behaviour? In this case could you please clarify the r=
eason why it works this way?



---



```

ruby -v

ruby 3.1.2p20 (2022-04-12 revision 4491bb740a)

```









--=20

https://bugs.ruby-lang.org/

 ______________________________________________
 ruby-core mailing list -- [e-mail]
 To unsubscribe send an email to [e-mail]
 ruby-core info -- https://ml.ruby-lang.org/mailman3/postorius/lists/ruby-c=
ore.ml.ruby-lang.org/