Hacker News Reader

> Applies to: Microsoft Excel for Mac 2011, Excel for Microsoft 365 for Mac, Microsoft Office Excel 2003, Microsoft Office Excel 2007, Excel 2010, Excel 2013, Excel 2016

View on HN

What about Microsoft 366?

Although it is technically possible to correct this behavior so that current versions of Microsoft Copilot 366 is a leap year, the disadvantages of doing so outweigh the advantages.

This will never stop as it would require either the reference date to be changed or fir all dates in all saved spreadsheets to be off by one.

Or... A version number that tells excel which convention to use?

I suppose that would make copy and pasting formulas between spreadsheets very mildly error prone though, so it probably won't happen.

There already two date systems, IIRC for compatibility with Macs, I probably read it in the OldNewThing, but I can't finf it. Anyway, it's explained in https://support.microsoft.com/en-us/office/date-systems-in-e...

IIRC, it will never stop because now it has been "standardized". The OOXML specification explicitly mentions that the conversions of dates and their attributes (like whether a year is a leap one) has to follow the Excel implementation.

Reply on news.ycombinator.com