Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow offset to be specified in ZonedDateTime text handling #171

Closed
GoogleCodeExporter opened this issue Mar 15, 2015 · 4 comments
Closed

Allow offset to be specified in ZonedDateTime text handling #171

GoogleCodeExporter opened this issue Mar 15, 2015 · 4 comments
Milestone

Comments

@GoogleCodeExporter
Copy link

@GoogleCodeExporter GoogleCodeExporter commented Mar 15, 2015

In order to reliably round-trip a ZonedDateTime around DST changes, we need to 
have a field specifier for the offset. So for example, a full round trip value 
might be:

    2013-01-16T14:21:03.1234567 Europe/London +00

Original issue reported on code.google.com by jonathan.skeet on 16 Jan 2013 at 2:21

@GoogleCodeExporter
Copy link
Author

@GoogleCodeExporter GoogleCodeExporter commented Mar 15, 2015

Would we only include the field when the result was otherwise ambiguous?
(I'm not sure how much we care about the round-trip format being reasonably 
human-readable.)

Original comment by malcolm.rowe on 24 Jan 2013 at 10:19

@GoogleCodeExporter
Copy link
Author

@GoogleCodeExporter GoogleCodeExporter commented Mar 15, 2015

I don't think so - that seems like more complexity for little benefit.

Original comment by jonathan.skeet on 24 Jan 2013 at 10:30

@GoogleCodeExporter
Copy link
Author

@GoogleCodeExporter GoogleCodeExporter commented Mar 15, 2015

Original comment by malcolm.rowe on 25 Jan 2013 at 9:23

  • Added labels: Milestone-1.2.0
@GoogleCodeExporter
Copy link
Author

@GoogleCodeExporter GoogleCodeExporter commented Mar 15, 2015

Fixed in revision 517b17be15c3.

We still don't have user documentation for ZonedDateTimePattern or 
OffsetDateTimePattern, but that can come when we've worked out what to do about 
standard patterns.

Original comment by jonathan.skeet on 9 Apr 2013 at 8:13

  • Changed state: Fixed
@malcolmr malcolmr modified the milestone: 1.2.0 Mar 15, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants