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 540198 - date parse failure
date parse failure
Status: RESOLVED FIXED
Product: Gnumeric
Classification: Applications
Component: General
1.8.x
Other All
: Normal normal
: ---
Assigned To: Jody Goldberg
Jody Goldberg
Depends on:
Blocks:
 
 
Reported: 2008-06-25 18:34 UTC by rigoberto
Modified: 2008-08-26 02:18 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
sample file, note the alignment of B1 (1.85 KB, application/x-gnumeric)
2008-08-24 19:45 UTC, Jody Goldberg
Details

Description rigoberto 2008-06-25 18:34:42 UTC
Please describe the problem:
i format whole column as date, then i enter "control-shift-;" (shortcut for today), and it doesnt get formatted

Steps to reproduce:
1. create spreadsheet
2. put "control-shift-;" in A1, B1, C1
3. format column A as: mmm/dd/yy, B as: dd-mmm-yy, C as: yyyy/mmm/dd
4. put "control-shift-;" in A2, B2, C2



Actual results:
the cell B2 doesn't get the right format (it appears as "6/25/2008")

Expected results:
the cell B2 should appear as "25-Jun-08"

Does this happen every time?
yes

Other information:
the A and C columns have no relation with the bug, i just included them because with A and C formats the bug doesn't occur, and dates are shown as expected
Comment 1 Jody Goldberg 2008-08-24 19:45:10 UTC
there is a bug here, an a possible feature request

1) the cell formatted with d-mmm-yyyy fails to parse the gnm_format_for_date_editing.

2) should we consider displaying the editable format using the assigned format if it is a date fmt with full year/month/day detail ?
Comment 2 Jody Goldberg 2008-08-24 19:45:55 UTC
Created attachment 117312 [details]
sample file, note the alignment of B1
Comment 3 Morten Welinder 2008-08-25 00:34:38 UTC
Re 2, if the number was also a integer, I think that would be a reasonable
thing to do.  I don't know if it would be confusing, though.
Comment 4 Morten Welinder 2008-08-26 02:18:52 UTC
(1) fixed.  I do not think (2) really needs to be done, but if it does,
that is a separate bug.