Issue #9521 has been updated by Akira Tanaka.


It seems the original document of that part written by gsinclair used GMT.
But I mistakenly modified to use JST.

I agree that most examples uses EST.
This convention is inherited from time.c.  
time.c has a sentence:
"All of these examples were done using the EST timezone which is GMT-5."

Also, I didn't considered well the behavior of Time.parse when multiple time zones are involved.

So I modified the example to use EST,
not only the result but also for "now" at r45838.


----------------------------------------
Bug #9521: [Doc] Fix error in Time.parse documentation (in lib/time)
https://bugs.ruby-lang.org/issues/9521#change-46562

* Author: Marcus Stollsteimer
* Status: Closed
* Priority: Normal
* Assignee: Zachary Scott
* Category: doc
* Target version: 
* ruby -v: ruby 2.1.0p0 (2013-12-25 revision 44422) [i686-linux]
* Backport: 1.9.3: UNKNOWN, 2.0.0: UNKNOWN, 2.1: UNKNOWN
----------------------------------------
The docs state that the examples are for GMT as local time zone while in fact they are for JST.
The patch fixes this by using EST (and saying so), like the rest of the examples for lib/time.


---Files--------------------------------
doc_lib_time.patch (1.13 KB)


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