Slashdot Mirror


Big Tech Warns of 'Japan's Millennium Bug' Ahead of Akihito's Abdication (theguardian.com)

MightyMartian shares a report from The Guardian: On April 30, 2019, Emperor Akihito of Japan is expected to abdicate the chrysanthemum throne. The decision was announced in December 2017 so as to ensure an orderly transition to Akihito's son, Naruhito, but the coronation could cause concerns in an unlikely place: the technology sector. The Japanese calendar counts up from the coronation of a new emperor, using not the name of the emperor, but the name of the era they herald. Akihito's coronation in January 1989 marked the beginning of the Heisei era, and the end of the Shwa era that preceded him; and Naruhito's coronation will itself mark another new era. But that brings problems. For one, Akihito has been on the throne for almost the entirety of the information age, meaning that many systems have never had to deal with a switchover in era. For another, the official name of Naruhito's era has yet to be announced, causing concern for diary publishers, calendar printers and international standards bodies. It's why some are calling it "Japan's Y2K problem." "The magnitude of this event on computing systems using the Japanese Calendar may be similar to the Y2K event with the Gregorian Calendar," said Microsoft's Shawn Steele. "For the Y2K event, there was world-wide recognition of the upcoming change, resulting in governments and software vendors beginning to work on solutions for that problem several years before January 1, 2000. Even with that preparation many organizations encountered problems due to the millennial transition. Fortunately, this is a rare event, however it means that most software has not been tested to ensure that it will behave with an additional era."

Unicode's Ken Whistler wrote in a message earlier this month: "The [Unicode Technical Committee] cannot afford to make any mistakes here, nor can it just *guess* and release the code point early. All of this is pointing directly to the necessity of issuing a Unicode 12.1 release sharply on the heels of Unicode 12.0, incorporating the addition of the new Japanese era name character, which all vendors will be under great pressure to immediately support in 2019 software releases."

18 of 211 comments (clear)

  1. Oh damn! by RobinH · · Score: 4, Funny

    When Jesus comes back do we need to reset the year back to zero? Crap, as a programmer I hate our calendar system(s)!

    --
    "I have never let my schooling interfere with my education." - Mark Twain
    1. Re:Oh damn! by ShanghaiBill · · Score: 5, Funny

      Crap, as a programmer I hate our calendar system(s)!

      Me too. It would be so much simpler if the earth rotated the sun in exactly 256 days, divided into exactly eight 32 day months.

    2. Re:Oh damn! by Opportunist · · Score: 3, Funny

      Right, what computer illiterate idiot designed this system?

      --
      We used to have a Bill of Rights. Now, with the rights gone, all we have left is the bill.
    3. Re:Oh damn! by RobinH · · Score: 5, Informative

      Well, I've always thought the International Fixed Calendar was a decent attempt at sanity, but if there's people in the world that can't adopt the metric system, there's no way in hell the calendar could change.

      --
      "I have never let my schooling interfere with my education." - Mark Twain
    4. Re:Oh damn! by AmiMoJo · · Score: 4, Interesting

      Interestingly in this case it probably won't be the numerical side of things that causes problems. Most IT systems use the same Gregorian calendar we do, and have a conversion function to handle translation to/from imperial eras.

      The problem is that, like leap seconds, there is no way to predict when eras will change so you have to update all your software every time there is a new one. Particularly for systems that handle personal data it's still common for people to enter their birthday using the imperial era system, so when the new era starts all those systems need to be able to handle it.

      It was bad enough the last time it happened, but this time IT is much more pervasive and user facing. All sorts of industries are affected, e.g. airlines need to be able to handle children born in the new era from day one.

      --
      const int one = 65536; (Silvermoon, Texture.cs)
      SJW, n: "Someone I don't like, and by the way I'm a fuckwit" - AC
    5. Re:Oh damn! by xxxJonBoyxxx · · Score: 3, Insightful

      >> When Jesus comes back do we need to reset the year back to zero?

      Serious answer: No, because the current calendar is based on the BIRTH of Christ.

      https://en.wikipedia.org/wiki/Anno_Domini

      If Jesus comes back "in glory" it's unlikely that he'll be back as an infant (unless your a Stewie fan), so your timekeeping based on the birth of a highly religious infant should remain intact. Whether or not He will need clocks in the eternal world to come remains up for debate.

      https://en.wikipedia.org/wiki/Second_Coming

    6. Re: Oh damn! by guruevi · · Score: 3, Informative

      It's not uncommon either. Pregnant people can go in labor weeks early, stress of flying often exacerbates the issue.

      --
      Custom electronics and digital signage for your business: www.evcircuits.com
    7. Re:Oh damn! by terrycarlino · · Score: 4, Interesting

      Its even more complicated than that. The second is a fundamental unit, so there are lots of other units which depend upon it's value. Change that and you've changed the value of the Hz, erg, amp,etc.. According to Wikipedia of the 22 names derived units only 3 do not depend on the second.

  2. Re:So... by Opportunist · · Score: 3

    I'm pretty sure it will be known in IT circles as the "placeholder era", and decades from now we'll find something along these lines in a lot of code...

    --
    We used to have a Bill of Rights. Now, with the rights gone, all we have left is the bill.
  3. Fake news! by Jesus+H+Rolle · · Score: 3, Interesting

    Japanese regnal years are not used for any significant calculations. Behind the scenes it's YYYY, with regnal years used only for display. This is an aesthetic issue only, and hardly unforeseen.

    1. Re:Fake news! by nojayuk · · Score: 4, Insightful

      Heisei calendaring appears on official documents, train tickets etc. (quick check, a Japan Rail reserved-seat ticket I was issued back on the 12th of May this year has the date of issue as 30.-5.12, that is Heisei year 30, month 5, day 12). Nearly all common date expressions in Japan use Christian Era numbering though.

    2. Re:Fake news! by Rei · · Score: 3, Interesting

      Apart from things like minor transportation delays, radiation monitors sounding, credit cards failing to work, some phones deleting new messages rather than old when running out of space, etc, probably the worst Y2K bug I heard of was a bunch of expectant mothers in the UK being falsely told that their children were at a high risk of Downs' Syndrome when they weren't, and vice versa, due to miscalculation of the mother's age. There were some abortions in the former group as a result of the email. Still, given all the hype, the actual effects were (as everyone here expected) quite small.

      My favorite was when the government of Maine started issuing titles to peoples' new cars describing it as a "Horseless Carriage", as apparently that had been hard-coded as the terminology for vehicles from before 1916. ;)

      --
      "Lock and load, Brides of Christ!"
  4. Explanation of the problem by Zontar_Thing_From_Ve · · Score: 5, Informative

    Officially years in Japan start with 1 and the coronation of the new emperor. Now it seems that the year in Japan is Heisei 30, which means it's the 30th year since the Heisei emperor (Akihito) took the throne. This would be something like in the US calling 2016 as Obama 8 or 2018 by the term Trump 2. The real problem here isn't that computers are going to shut down in Japan when the current emperor abdicates next year as planned. This isn't really a Y2K problem. The Guardian usually does good work but to say this is similar to Y2K is just not correct. The article even admits that some older computers have actually never updated the year from the Showa era (when Hiirohito was emperor) so they think this year is Showa 93. Those computers will have a problem in 2025 as their calendars were never designed to hold 3 digit years, which would make 2025 be Showa 100. The real problem with the abdication is that the next era for the upcoming emperor has not yet been named. OK, so why is that a problem? Well, Japan has a history of creating a brand new character for the era when it change and Unicode has a major release scheduled for right before the abdication is scheduled to happen. The brand new character is the problem because the next release of Unicode won't support it because nobody knows what it will be yet. They have the ability to guess, but nobody wants to guess because they could be wrong. So all this hubbub is that next year's major Unicode release will require a patch shortly after release with the patch including the new character for the new era. Do keep in mind that Akihito could die of natural causes before the abdication and this problem will happen immediately upon his death. And this problem will happen every time a new emperor takes over. I'm not convinced that this is really a major problem. Computers could easily just show Heisei 31 and so on until the Unicode fix is in place. I guess it's just fun on a slow news day to blow things out of proportion.

    1. Re:Explanation of the problem by omnichad · · Score: 3, Informative

      If Unicode was at least sane enough, there would be a range of consecutive reserved codepoints. However, 0x337A is already assigned to something else (as is 0x337F if they started going in the other direction). Having a character doesn't matter as much as having a reserved codepoint. You can test without a real character.

  5. will they also fix the 2038 bug as well? by Joe_Dragon · · Score: 3, Insightful

    will they also fix the 2038 bug as well?
    or hold off so they have jobs in 2037 fixing it.

  6. Re:All commonly used calendars are bonkers by Diss+Champ · · Score: 3, Informative

    Regarding a non-7 day week, this has been tried before and didn't work. See for example www.mdpi.com/2075-4698/3/4/399/pdf

    Sometimes a long-followed social construct has survived because it works well for us animals, and if that makes it harder for programming computers that is a reasonable cost.

  7. "The Shwa era"? 8-Bit Slashdot wins again by rxmd · · Score: 5, Funny

    Akihito's coronation in January 1989 marked the beginning of the Heisei era, and the end of the Shwa era that preceded him

    Actually it's not the Shwa era, but the Showa era, with a bar on top of the o. The character in question (U+014D) is used in transliterating Japanese in Latin script to indicate pronunciation. It has been part of Unicode since 1991.

    It's interesting to see in the summary a discussion of Unicode 12.1 vs. 12.0, when Slashdot itself doesn't support the Unicode 1.0 characters necessary to write the summary :)

    --
    As a state gets corrupt, its laws multiply; the most corrupt states have the most numerous laws. (Tacitus, Annales 3:27)
  8. Re:So... by SinGunner · · Score: 4, Informative

    Japanese "eras" have only been tied directly to the emperor since the Meiji Restoration (mid-1800's). The current era is only the 4th since this change. The Emperor takes a new name when they ascend the throne, so there has never been a way to know the name of the era in advance. Given the intense superstition prevalent in Japanese society, it seems incredibly unlikely a name would ever be disseminated in advance.