Created attachment 117001 [details] CSV example file containing identically formatted dates, some correctly imported and some not. How to reproduce: - Import the example CSV file (Insert -> Sheet from file) - Set language to "English (UK)" or "English (US)" - Import as single column (deselect all Separator options) - Set the column type to "Date (DMY)" - Press OK Expected result: All rows are interpreted correctly as date values Actual result: 3 rows are not imported as date values: 31 Mar 2013, 02:00 30 Mar 2014, 02:00 29 Mar 2015, 02:00 The offending pattern seems to be: (31-n) + " Mar " + (2013+n) + ", 02:00" Other date fields with 02:00 seem unaffected. Seen in: - OpenOffice.org 3.3.0; OOO330m20 (Build:9567) on Windows 7 (64-bit) - LibreOffice 4.4.3.2, Build ID: 40m0(Build:2), Locale: en_GB on openSuSE 13.1 (64-bit) - LibreOffice 5.0.0.2.0+, Build ID: 2fa23d10c32f77da121ecf03f77ff3f10ca0d580, Locale: en-GB (en_GB.UTF-8) on openSuSE 13.1 (64-bit)
Confirmed. The problematic ones are imported as number. Win 7 Pro 64-bit Version: 5.1.0.0.alpha1+ (x64) Build ID: 3a6ec53eeeec71312f5ea890689f9c2ee79c2aac TinderBox: Win-x86_64@62-TDF, Branch:MASTER, Time: 2015-07-01_02:24:40 Locale: fi-FI (fi_FI)
Created attachment 117012 [details] File sample with more dates to test Adding more rows with a different month the issue change from hour 02:00 to year 2013. 31/03/13 01:00 31 Mar 2013, 02:00 31/03/13 03:00 30/03/14 01:00 30 Mar 2014, 02:00 30/03/14 03:00 29/03/15 01:00 29 Mar 2015, 02:00 29/03/15 03:00 31 Apr 2013, 01:00 31 Apr 2013, 02:00 31 Apr 2013, 03:00 30/04/14 01:00 30/04/14 02:00 30/04/14 03:00 29/04/15 01:00 29/04/15 02:00 29/04/15 03:00 using comma as separator, the problem remains with 2013 year. 31/03/13 01:00 31/03/13 02:00 31/03/13 03:00 30/03/14 01:00 30/03/14 02:00 30/03/14 03:00 29/03/15 01:00 29/03/15 02:00 29/03/15 03:00 31 Apr 2013 01:00 31 Apr 2013 02:00 31 Apr 2013 03:00 30/04/14 01:00 30/04/14 02:00 30/04/14 03:00 29/04/15 01:00 29/04/15 02:00 29/04/15 03:00
This seems to be due to daylight saving time (DST) switches. In an en-US locale DST transition is on the last Sunday of March, which were 31-Mar-2013, 30-Mar-2014 and 29-Mar-2013. Technically there are no times between 02:00 and 02:59:59.999 on these dates. Need to investigate why these DST switches apparently affect date recognition also in other locales. @m.a.riosv: Of course 31 Apr 2013 remains string because there is no April 31 ;-)
> @m.a.riosv: > Of course 31 Apr 2013 remains string because there is no April 31 ;-) Pity, one day per year, they would be a couple of months in a life. :)
*** Bug 92892 has been marked as a duplicate of this bug. ***
** Please read this message in its entirety before responding ** 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 on a currently supported version of LibreOffice (5.1.5 or 5.2.1 https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System 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) http://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: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug-20160920
Reproduced in LOdev: Version: 5.3.0.0.alpha0+ Build ID: 075489b4b810692edc2ba9910eb3ca659a2b6745 CPU Threads: 4; OS Version: Linux 3.12; UI Render: default; Locale: en-GB (en_GB.UTF-8); Calc: group
** Please read this message in its entirety before responding ** 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 http://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://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
Took a more detailed look into this after a long time. Fun stuff.. or not. The calendar is always created with the time zone of the system as default, so for most Europeans something with CET (normal time) or CEST (summer daylight saving time). Then 2013-03-31 and the other two dates indeed were DST transition dates, there simply is no 02:00 to 02:59:59.999 for those days in Europe. Not sure how to solve this except for all Gregorian based calendars use always the UTC time zone, which is not DST afflicted. It wouldn't fit the general assumption that times are entered (and thus displayed) in the local time zone, but then again there are no conversions to/from time zones or time zone aware calculations at all, all times are "as is".
Eike Rathke committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/+/942de6a01ba990e5f3bc55ce4ab3737a03f67f39%5E%21 Resolves: tdf#92503 introduce TimeZone to calendar loading and default to UTC It will be available in 6.4.0. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
Eike Rathke committed a patch related to this issue. It has been pushed to "libreoffice-6-3": https://git.libreoffice.org/core/+/a9c02d543987a0c05beda19905ccd6fb4263b592%5E%21 Resolves: tdf#92503 introduce TimeZone to calendar loading and default to UTC It will be available in 6.3.0.1. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
Xisco Fauli committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/efda4f52ea59e2d235a55be863fbffa8ca7a7874 tdf#92503: sc: Add UItest It will be available in 7.3.0. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.