Apache OpenOffice (AOO) Bugzilla – Issue 86094
Date is automatically decremented on input
Last modified: 2013-08-07 15:14:39 UTC
(Follow up for issue 76623) Using 2.4m6 on Vista with Russian localle and Moscow time zone Calc autodecrements date 01.07.1919 (and earlier) on input. Dates after 01.07.1919 are fine.
add CC
Hopefully we would not miss 3.0.
Will try.
Two months left after last comment. Is there any progress?
Not yet, other things to do. Stay tuned, as you're on Cc you'll be notified on status changes.
I can't reproduce this using DEV300_m15 on Windows XP, set Regional Settings to Russian and Location to Russia. Did this vanish? Could someone check please? Probably not doable in 3.0 time frame, retargeting to 3.1
Not being able to reproduce it actually was my inability to operate Windows, as it simply doesn't allow a non-admin user to change timezone. I did reproduce it on Linux using TZ=Europe/Moscow Reassigning to my spare time account and retargeting to 3.0 again.
*** Issue 90627 has been marked as a duplicate of this issue. ***
From issue 90627: TZ=America/St_Johns and dates <= 1935-03-30 exhibit same behavior.
Holy nastiness.. time zones change on those dates and include seconds: TZ=Europe/Moscow date <= 1919-07-01 time zone offset +2:30:48 instead of +3:00 Additionally DST +2h instead of +1h TZ=America/St_Johns date <= 1935-03-30 time zone offset -3:30:52 instead of -3:30 1935-03-30 00:00:00 => 1935-03-29 23:59:08
This turned out to be more complicated. Even if during input the value internally can be compensated for the seconds offset, during output/display/retrieval of the value the OOo UNO API for the calendar lacks resolution for these timezone offsets, current minimum resolution is minutes, and the result is still wrong in some cases. The API needs to be enhanced to allow for a more fine grained resolution of seconds respectively milliseconds, without going incompatible of course :( Retargeting to OOo3.1
Reported on IRC: TZ=Finland/Helsinki date <= 1916-07-28
Eike, are we on track for 3.1 with fix for this issue? Thanks.
I think so.
In cws locales31: offapi/com/sun/star/i18n/CalendarFieldIndex.idl 1.12.128.1 i18npool/inc/calendar_gregorian.hxx 1.16.24.1 i18npool/source/calendar/calendar_gregorian.cxx 1.34.24.1 unotools/inc/unotools/calendarwrapper.hxx 1.10.24.1 unotools/source/i18n/calendarwrapper.cxx 1.15.24.1 svtools/source/numbers/zforfind.cxx 1.51.96.1 Also checked the cases of issue 76623, they're still good. Note that the case of TZ=Finland/Helsinki mentioned above would be TZ=Europe/Helsinki instead. However, I could not reproduce a faulty behavior with the date given or around. Also dumping calendar internals around that date did not reveal timezone or DST transitions.
Reassigning to QA for verification.
Great, thanks a lot!
verified in internal build cws_locales31
Same problem in Pt-BR locale. At this moment we are in Summer Time (GMT -2h). Best regards, Renato
renatoyamane, do you see this issue in 3.1?
This issue is closed automatically and wasn't rechecked in a current version of OOo. The fixed issue should be integrated in OOo since more than half a year. If you think this issue isn't fixed in a current version (OOo 3.1), please reopen it and change the field 'Target Milestone' accordingly. If you want to download a current version of OOo => http://download.openoffice.org/index.html If you want to know more about the handling of fixed/verified issues => http://wiki.services.openoffice.org/wiki/Handle_fixed_verified_issues
Sorry this issue was wrongly closed. This issue will be reopened automatically. And will be set after that back to fixed/verified.
Set to state 'fixed'.
Set back to state 'verified/fixed'. Again. Sorry for the mass of mails.
*** Issue 103240 has been marked as a duplicate of this issue. ***
Still exists in 3.1.1 Windows version. Timezone Europe/Tallinn, locale Estonian Entering 1.3.1790 results 28.02.1790
Created follow-up issue 105864 for the latest Europe/Tallin case because it is slightly different, see there.
Resetting to verified.
This issue is closed automatically. It should be fixed in a version with is available for longer than half a year (OOo 3.1). If you think this issue isn't fixed in the current version (OOo 3.2) please reopen it. But then please pay attention about the field 'target milestone'. The closure was approved by the Release Status Meeting at 22nd of February 2010 and it is based on the issue handling guideline for fixed/verified issues : http://wiki.services.openoffice.org/wiki/Handle_fixed_verified_issues