Issue 8281

Summary: date error
Product: Calc Reporter: cgreco <cgreco>
Component: codeAssignee: oc
Status: CLOSED DUPLICATE QA Contact: issues@sc <issues>
Severity: Trivial    
Priority: P3 CC: email, issues, kyoshida
Version: 643   
Target Milestone: ---   
Hardware: PC   
OS: Linux, all   
Issue Type: DEFECT Latest Confirmation in: ---
Developer Difficulty: ---
Attachments:
Description Flags
TEST CASE WITH ACTIONS / RESULTS UNDER DIFFERENT LOCALE SETTINGS
none
Self-explanatory sample file with actions / results under different system locale settings none

Description cgreco 2002-10-13 00:27:47 UTC
Date displayed by OpenOffice643 from an Excel spreadsheet is one day less than
that reported by Excel and StarOffice6.0, i.e., cell value 37523 displayed as
09/23/02 in OpenOffice643 and 09/24/02 in Excel and StarOffice6.0.
Comment 1 kyoshida 2002-10-15 19:31:55 UTC
I've noticed this too.

I've seen this happen in both the Linux and Windows versions of 643.

Kohei
Comment 2 daniel.rentz 2002-10-16 08:48:43 UTC
*** Issue 8375 has been marked as a duplicate of this issue. ***
Comment 3 pbryan 2002-10-17 05:10:21 UTC
Easy reproduction scenario: new spreadsheet, enter the following
formula into a cell: =TODAY(). You'll see that the resulting date is
yesterday.
Comment 4 kyoshida 2002-11-01 14:01:18 UTC
Actually all it takes to reproduce this is to just type in a date in a
cell.  For example, when I type 10/23/2002, it becomes 10/22/2002 when
entered.
Comment 5 daniel.rentz 2002-11-11 15:17:55 UTC
*** Issue 9133 has been marked as a duplicate of this issue. ***
Comment 6 prgmgr 2002-11-21 00:34:26 UTC
*** Issue 8954 has been marked as a duplicate of this issue. ***
Comment 7 afunke 2002-11-23 22:49:29 UTC
While running OpenOffice.org build 643C on
Linux i686 - kernel 2.4.19 - libc 2.2.4

1. I've originally seen this bug while system locale was set to its
default (America/Sao_Paulo - BRST), with RTC/hwclock stored as UTC.
Currently the DAYLIGHT SAVINGS TIME is active at this time zone. What
I see is:


     =TODAY() results in one day less than today

     Entering a number (for example, number 0) results in a displayed
date that is one day less than the expected date (expected
30.dec.1899, displayed 29.dec.1899);

     Entering any date (e.g. 30.dec.1899) results in displaying the
typed date, but formatting the date as default reveals that the number
is the expected number plus 1 (e.g., 1)


2. After I changed the system locale to "Europe/Berlin" (CET), then:

 =TODAY() results in correct date (today);

but typing any date from 01.apr.2002 to 27.oct.2002 results in
subtraction of one day from the date "number", and the displayed date
is one day less than the typed date;

entering any number (for example, number 0) and formatting as date
shows the correct corresponding date (e.g., 30.12.1899);

I hope this information can be useful in some way.
Comment 8 afunke 2002-11-24 12:30:05 UTC
Created attachment 3721 [details]
TEST CASE WITH ACTIONS / RESULTS UNDER DIFFERENT LOCALE SETTINGS
Comment 9 afunke 2002-11-24 12:32:11 UTC
Created attachment 3722 [details]
Self-explanatory sample file with actions / results under different system locale settings
Comment 10 daniel.rentz 2002-11-25 11:20:01 UTC
*** Issue 9505 has been marked as a duplicate of this issue. ***
Comment 11 ooo 2002-11-25 12:07:17 UTC
This indeed was a timezone glitch and was fixed in the 644 build line.
You may try the changes of the following files and revisions:

svtools/source/numbers/zforfind.cxx  1.27, 1.29
svtools/source/numbers/zformat.cxx  1.45
unotools/inc/unotools/calendarwrapper.hxx  1.6
unotools/source/i18n/calendarwrapper.cxx  1.8
Comment 12 daniel.rentz 2002-12-06 07:49:34 UTC
*** Issue 9900 has been marked as a duplicate of this issue. ***
Comment 13 frank 2002-12-20 08:43:21 UTC
*** Issue 10228 has been marked as a duplicate of this issue. ***
Comment 14 oc 2003-01-10 11:48:00 UTC
Reopened for changing status
Comment 15 oc 2003-01-10 11:48:59 UTC
Will be fixed with 9132

*** This issue has been marked as a duplicate of 9132 ***
Comment 16 oc 2003-01-10 11:49:21 UTC
Closed because duplicate
Comment 17 frank 2003-01-14 14:26:40 UTC
*** Issue 10654 has been marked as a duplicate of this issue. ***
Comment 18 frank 2003-01-14 14:28:43 UTC
*** Issue 10654 has been marked as a duplicate of this issue. ***
Comment 19 frank 2003-01-16 15:58:41 UTC
*** Issue 10707 has been marked as a duplicate of this issue. ***
Comment 20 daniel.rentz 2003-01-20 08:31:49 UTC
*** Issue 10749 has been marked as a duplicate of this issue. ***
Comment 21 frank 2003-02-17 08:09:55 UTC
*** Issue 11508 has been marked as a duplicate of this issue. ***
Comment 22 frank 2003-03-20 07:53:05 UTC
*** Issue 12484 has been marked as a duplicate of this issue. ***