From 4bfca0be00a02aa2a0f211c47ed73abc6ddf5054 Mon Sep 17 00:00:00 2001 From: Morten Haraldsen Date: Mon, 12 Aug 2019 07:30:39 +0200 Subject: [PATCH] Update README.md --- README.md | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/README.md b/README.md index b325d15..1ede6b7 100644 --- a/README.md +++ b/README.md @@ -91,7 +91,5 @@ Such offset is described in RFC3339 section 4.3., named "Unknown Local Offset Co is the preferred reference point for the specified time. ### Leap second parsing -Since Java's `java.time` classes do not support storing leap seconds, it is not obvious how to support this. - -ITU will parse the date-time correctly, however storing such values is not possible (in a `java.time.OffsetDateTime`), the `60` is therefore abandoned and the date-time will use `59` instead of `60`. +Since Java's `java.time` classes do not support storing leap seconds, ITU will throw a `LeapSecondException` if one is encountered to signal that this is a leap second. The exception can then be queried for the second-value. Storing such values is not possible in a `java.time.OffsetDateTime`, the `60` is therefore abandoned and the date-time will use `59` instead of `60`.