The reason Google and Jisho translate うるう秒 as “leap second” and Bing as “leap
seconds” is that both translations are technically correct. Nouns in Japanese
are not normally marked as singular or plural. That said, since leap seconds
occur one at a time, the more appropriate translation would
Hi Kevin,
Kevin Birth wrote:
For anyone curious about how Japan is handling the leap second, since it
is occurring at 8:59:59 in the morning on a business day, the following
two articles refer to the solution that Japanese financial exchanges are
using a mini leap smear spread over two hours
For anyone curious about how Japan is handling the leap second, since it is
occurring at 8:59:59 in the morning on a business day, the following two
articles refer to the solution that Japanese financial exchanges are using―a
mini leap smear spread over two hours before the opening bell.
The
On Jun 23, 2015, at 6:00 AM, Kevin Birth kevin.bi...@qc.cuny.edu wrote:
For anyone curious enough to search for information online about the leap
second in Japan, the Japanese term for leap second is:
うるう秒
And indeed Google and Jisho translate that as leap second. For some reason
Bing
With regard to NTP, the following link discusses it some. Unfortunately, this
time Google translate really botches things. My reading (and my Japanese is
not that great) is that this telecomm company’s server will sync to NTP, but it
will send out a leap smear over a couple of hours to the
On Tue, Jun 23, 2015 at 03:47:49PM +0200, Martin Burnicki wrote:
I really doubt that real NTP clients can follow a server smearing a leap
second over 2 hours only.
You mean a client using default configuration? With a reduced polling
interval I think it shouldn't be a big problem to follow
Mon Jun 22 21:00:29 UTC 2015
Mon Jun 22 21:00:54 UTC 2015
I had hoped this would be an easy way to find TAI, but it looks like I'll
have to parse the leapsec list.
You can get the TAI offset by converting those two strings back to a time_t.
--
These are my opinions. I hate spam.
