Issue 127150 - Entering date on cell with date format
Summary: Entering date on cell with date format
Status: CLOSED IRREPRODUCIBLE
Alias: None
Product: Calc
Classification: Application
Component: formatting (show other issues)
Version: 4.1.1
Hardware: PC Windows 8, 8.1
: P5 (lowest) Normal (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
URL:
Keywords: needmoreinfo
Depends on:
Blocks:
 
Reported: 2016-10-04 21:08 UTC by judos
Modified: 2017-05-20 09:57 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---

Attachments
sample calc document (9.16 KB, application/vnd.oasis.opendocument.spreadsheet)
2016-10-04 21:53 UTC, judos 		no flags Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
Description judos 2016-10-04 21:08:25 UTC 
I set a cell to have the custom format "DD.MM".
Now when I enter 04.10 it will change the value to "03.01.1900" which does not make any sense.
I would assume the entered content is always parsed with the configured date format when I press enter. This seems however not to work for custom date formats.

Thanks for having a look!
Comment 1 Marcus 2016-10-04 21:19:35 UTC 
I cannot reproduce your reported problem. When formatting a cell with "DD.MM" and entering "04.10" than I get "04.10" in the cell.

Please can you attach a sample document to this issue? That would be very to see what details you have done so far.

Thanks
Comment 2 judos 2016-10-04 21:53:54 UTC 
Created attachment 85712 [details]
sample calc document

I added a sample document where I just reproduced the problem.
Comment 3 Marcus 2016-10-04 22:15:54 UTC 
Thanks for the sample file. At least on Linux with AOO 4.1.2 it's not happening for me. When entering "18.5" into cell A1, then it stays - or better said it's "18.05" with a leading zero for the day.

Tomorrow I'll test on Windows. Maybe there is a difference.
Comment 4 Marcus 2016-10-05 09:46:40 UTC 
On Windows 10 with 4.1.2 it is also not occurring. So, maybe it's worth to update. But when youdecide so, please wait a few days. Then you can update right away to the upcoming 4.1.3 release.

For the moment I'll set this issue to irreproducible. Maybe someone else has more success.
Comment 5 mroe 2016-10-05 10:25:48 UTC 
It seems it belongs to the used LOCALE.
I think there is a locale setting (maybe with a special language) where the point is the decimal separator. So 4.10 will be 4 → 03.01.1900 + 0.10 → 09:36:00