After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 603116 - Number matching "Sep 23 2008"
Number matching "Sep 23 2008"
Status: RESOLVED FIXED
Product: Gnumeric
Classification: Applications
Component: General
git master
Other All
: Normal critical
: ---
Assigned To: Jody Goldberg
Jody Goldberg
Depends on:
Blocks:
 
 
Reported: 2009-11-27 07:51 UTC by jbordall
Modified: 2009-11-27 14:42 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description jbordall 2009-11-27 07:51:20 UTC
I imported a tab-delimited text file using the Advanced --> Text feature of the Open dialog box. The text file was composed of 3 columns and only 960 rows of data. Each line was CR/LF (MS-DOS) terminated. I specified the first column as Text, the second column as a Date field (m/d/yy), and the third as a Number.

A sample of one row:
"admin <TAB> Sep 23 2008 <TAB> 34"

Then, it imported the text and noticed that all the years in the Date column were converted to "09". Hence, the example from above was converted to "admin <TAB> 9/23/09 <TAB> 34". Obviously, "09" is a year away from "08"!

I worked around this by doing a query with a different date format, mm/dd/yy, which imported correctly into my Gnumeric spreadsheet.

Please fix!

-Jonathan
Comment 1 jbordall 2009-11-27 07:53:09 UTC
BTW, I found this on Ubuntu Linux 8.04LTS from the binary package provided by Ubuntu. *No* custom-compiled applications were installed on this system.
Comment 2 Morten Welinder 2009-11-27 13:33:17 UTC
This happens even for the GUI.  We simply fail to understand that date
format, which is kind of strange.
Comment 3 Morten Welinder 2009-11-27 13:34:54 UTC
Specifically what happens is that 2008 is seen as a timestamp (20:08)
and the date that is now without year gets the current year tagged on.
Comment 4 Morten Welinder 2009-11-27 14:42:04 UTC
This problem has been fixed in the development version. The fix will be available in the next major software release. Thank you for your bug report.

http://git.gnome.org/cgit/gnumeric/commit/?id=450363c539fd021f983b4cd0c4effde528d3d650