As I just discovered, it's not possible to use a standard date for february 29th. It seems that leap years are not (yet) supported. Is it possible to implement that?
I am able to standardize 29 February 1904 and other leap years0
What exact date are you trying to standardized? All leap years are accepted just fine.
I have run across one example in which the person writing the record really did write Feb. 29 when it was not a leap year. In those rare situations, all you can do either enter the date as 29 February YYYY and link it with the standard of Feb. 29 or enter the date as 1 March YYYY based on the assumption that the event really did take place the day after Feb. 28 that year.
Or you have run across one exception to the rule for leap years that the current program did not account for. The rule for leap years now is that the year has to be divisible by 4 except for years ending in 00. Those have to be divisible by 400. So 1900 was not a leap year but 2000 was and 2100 will not be.3
@Gordon Collett Thx, offcourse I do know how to calculate a leap year. 🤭
I have 2 sources (scans of both birth and death record), which has clearly written february 29th, 1786. So I assumed the date being right and didn't do the math as I couldn't standardize it. 🥴
So I've learned the lesson (again): don't automaticly pressume the software is to blame, sometimes the human it to blame! 🤣🤣0
I've had a record record a baptism for November 31st. 🤣0