Version: 1.4.2 (using KDE 3.5.0, Debian Package 4:3.5.0-3 (testing/unstable)) Compiler: Target: x86_64-linux-gnu OS: Linux (x86_64) release 2.6.15.1 After converting an ods file make with openoffice To see problem, read provided ods file with kspread, saving it as a native kspread file. Stopping and restarting kspread (just to clear all) and reloading just saved file. in file now all the cells that contained a time only _seem_ to contain a time, however all calculations are 0 and when clicking on any cell with a time shows that they all contain the date 30/12/1899
Created attachment 14447 [details] original opendocument spreadsheet file This is the spreadsheet i used. it was produced with 32bit open office 2.0
Created attachment 14448 [details] resulting kspread file after saving in native file format here is the native file that was produced on my system from previous opendoc file (just in case the bug doesn't show on other peoples system).
I couldn't really test this, kspread in trunk was awfully slow in opening and saving the file, and I had to kill the process as it was eating my ram. bug this seems related to bug #173736
I'm seeing the same thing here. I opened a ods file, and saved back as ods, and the time cells are all wrong when opening in openoffice.
Thank you for the bug report. As this report hasn't seen any changes in 5 years or more, we ask if you can please confirm that the issue still persists. If this bug is no longer persisting or relevant please change the status to resolved.
This bug may have been resolved or not. I would not know. I have not been using KOffice since a long time. I suspect it is no longer relevant since there have been quite a few KDE releases since. As far as I am concerned the bug may be closed. Cheers, Ernest. > On 9 Mar 2021, at 23:43, Justin Zobel <bugzilla_noreply@kde.org> wrote: > > https://bugs.kde.org/show_bug.cgi?id=121009 > > --- Comment #5 from Justin Zobel <justin.zobel@gmail.com> --- > Thank you for the bug report. > > As this report hasn't seen any changes in 5 years or more, we ask if you can > please confirm that the issue still persists. > > If this bug is no longer persisting or relevant please change the status to > resolved. > > -- > You are receiving this mail because: > You reported the bug.