Bug 144687

Summary:	ISLEAPYEAR gives FALSE for years displaying Feb 29th
Product:	LibreOffice	Reporter:	Mike Kaganski <mikekaganski>
Component:	Calc	Assignee:	Not Assigned <libreoffice-bugs>
Status:	NEW ---
Severity:	normal	CC:	79045_79045, xiscofauli
Priority:	medium
Version:	3.4.0 release
Hardware:	All
OS:	All
See Also:	https://bugs.documentfoundation.org/show_bug.cgi?id=96756 https://bugs.documentfoundation.org/show_bug.cgi?id=144678 https://bugs.documentfoundation.org/show_bug.cgi?id=144692 https://bugs.documentfoundation.org/show_bug.cgi?id=144699
Whiteboard:
Crash report or crash signature:		Regression By:
Bug Depends on:
Bug Blocks:	108827

Description Mike Kaganski 2021-09-23 19:01:00 UTC

1. Enter number '-292127' in A1, and format as a date
   => it will show 1100-02-29
2. In B1, put formula '=ISLEAPYEAR(A1)'
   => it will show FALSE

The problem is that the date is before introduction of Gregorian calendar (1582-10-15); the serial dates from that period are displayed using Julian calendar, but ISLEAPYEAR uses proleptic Gregorian calendar to determine if the year is leap.

Comment 1 Andreas Heinisch 2021-09-24 09:13:29 UTC

Ongoing discussion: https://gerrit.libreoffice.org/c/core/+/122545

Comment 2 Xisco Faulí 2021-09-29 09:57:30 UTC

Moving to NEW

Comment 3 QA Administrators 2024-05-02 03:15:18 UTC Comment hidden (obsolete)

Dear Mike Kaganski,

To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year.

There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present.

If you have time, please do the following:

Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/

If the bug is present, please leave a comment that includes the information from Help - About LibreOffice.

If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice.

Please DO NOT

Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not
appropriate in this case)

If you want to do more to help you can test to see if your issue is a REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/

2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to 'inherited from OOo';
4b. If the bug was not present in 3.3 - add 'regression' to keyword

Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa

Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team

MassPing-UntouchedBug

Comment 4 Mike Kaganski 2024-05-02 05:45:18 UTC

Still repro using Version: 24.2.3.1 (X86_64) / LibreOffice Community
Build ID: fc604d5980a783e74808a001f1918a603d920494
CPU threads: 24; OS: Windows 10.0 Build 22631; UI render: default; VCL: win
Locale: en-GB (ru_RU); UI: en-GB
Calc: CL threaded