Bug 239751 - kspread:msoffice2003: Date format not retained correctly in kspread
Summary: kspread:msoffice2003: Date format not retained correctly in kspread
Status: RESOLVED WORKSFORME
Alias: None
Product: calligrasheets
Classification: Applications
Component: opendocument (other bugs)
Version First Reported In: unspecified
Platform: unspecified All
: NOR normal
Target Milestone: ---
Assignee: Marijn Kruisselbrink
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-04-27 13:21 UTC by Lassi Nieminen
Modified: 2023-01-19 05:15 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments
testdata to be opened in kspread (22.00 KB, application/vnd.ms-excel)
2010-04-27 13:21 UTC, Lassi Nieminen
Details
screenshot of the document in kspread (171.70 KB, image/png)
2010-04-27 13:22 UTC, Lassi Nieminen
Details
screenshot of the document in msexcel (105.07 KB, image/png)
2010-04-27 13:22 UTC, Lassi Nieminen
Details
Screenshot in Latest Calligra Tables (117.42 KB, image/png)
2011-12-23 08:46 UTC, swathi
Details

Note You need to log in before you can comment on or make changes to this bug.
Description David Faure 2010-05-28 03:31:49 UTC


---- Reported by lassi.ta.nieminen@nokia.com 2010-04-27 14:21:52 +0300 ----

Created an attachment
testdata to be opened in kspread

SOFTWARE VERSION:
Kubuntu version 9.10
KOffice Version 1118926
Test Document(MS Office 2000): me00_date_formatting.xls

STEPS LEADING TO PROBLEM: 

1.Open the document in MS Office 2000.
2.Open the same document in Kspread.
3.Observe the date and time in the header.


EXPECTED OUTCOME:
kspread should be able to retain the date format correctly.Check rows
D6,7, 15 -17.
see attachment ms00_date_format_msexcel.png

ACTUAL OUTCOME:
kspread is unable to retain the date format correctly. "/" displayed instead
of "." in date formats.
see attachment ms00_date_format_kspread.png


FREQUENCY OF OCCURRENCE: 
Always



---- Additional Comments From lassi.ta.nieminen@nokia.com 2010-04-27 14:22:14 +0300 ----

Created an attachment
screenshot of the document in kspread



---- Additional Comments From lassi.ta.nieminen@nokia.com 2010-04-27 14:22:31 +0300 ----

Created an attachment
screenshot of the document in msexcel



--- Bug imported by faure@kde.org 2010-05-28 03:31  ---

This bug was previously known as _bug_ 165882.

Imported an attachment (id=47207)
Imported an attachment (id=47208)
Imported an attachment (id=47209)

Unknown bug field "example" encountered while moving bug
   <example>2010-04-27 14:22:31</example>

Comment 1 Marijn Kruisselbrink 2010-10-01 14:19:36 UTC
My version of excel displays row 6 and 7 the same as kspread does (and differently from the attached excel screenshot). For the format in row 17 I'm not sure what is happening, the xls file clearly specifies the cell to be formatted as m/d/yyyy, but somehow excel ignores that and replaces the slashes with dashes. Finally row 15 and 16 are formatted "to respond to changes in regional date and time settings that are specified for the operating system". So it is to be expected that these dates will not always be formatted in the same way.

So all in all I'd be inclined to say that there is no bug here (and certainly the "/" displayed instead of "." is not correct, as excel 2010 for me doesn't use dots in any of these date formats).
Comment 2 swathi 2011-12-23 08:46:32 UTC
Reopening the bug because issue is still there for the cells from D15 to D17.
Here the date should be displayed in format 10.01.2009  but in calligra tables these are displaying as 1/10/09.(Please check the attached screenshot in MS Excel 2000 and then compare).

Also in revision  efd72bd27341ffe9a49d4e30352f9468bb49d99d,Observe the date format in D18. Format of the date should be displayed as February 11,2009.But is is displaying as 2/11/2009.
Comment 3 swathi 2011-12-23 08:46:58 UTC
Created attachment 67045 [details]
Screenshot in Latest Calligra Tables
Comment 4 Andrew Crouthamel 2018-11-06 15:15:18 UTC
Dear Bug Submitter,

This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond.

Thank you for helping us make KDE software even better for everyone!
Comment 5 Andrew Crouthamel 2018-11-18 03:29:40 UTC
Dear Bug Submitter,

This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? This bug will be moved back to REPORTED Status for manual review later, which may take a while. If you are able to, please lend us a hand.

Thank you for helping us make KDE software even better for everyone!
Comment 6 Justin Zobel 2022-12-20 22:51:39 UTC
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version?

If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Comment 7 Bug Janitor Service 2023-01-04 05:24:47 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 8 Bug Janitor Service 2023-01-19 05:15:13 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!