You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Aug 13, 2025. It is now read-only.
When reading a 1900-01-02 date from excel, we got 1090-01-01. I found that was caused by incorrect TimeFromExcelTime logic because that is not consistent with the logid of Excel and WPS which consider 1900 as a leap year as compatible with the old lotus.
Convervation
Should we change the logic to makeit consistent with the excel Client so we can read the 'correct' cell date value befoe 1900-03-01, i think that is better.
Problem
When reading a 1900-01-02 date from excel, we got 1090-01-01. I found that was caused by incorrect TimeFromExcelTime logic because that is not consistent with the logid of Excel and WPS which consider 1900 as a leap year as compatible with the old lotus.
Convervation
Some Information
I found some meterial from internet, like https://learn.microsoft.com/en-us/troubleshoot/microsoft-365-apps/excel/wrongly-assumes-1900-is-leap-year, and i found that MS Office and WPS now both consider 1900 as a leap year for compatible.