Bug 45025 - Overwriting is not working as expected
Summary: Overwriting is not working as expected
Status: CLOSED WONTFIX
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
3.5.0 RC1
Hardware: x86-64 (AMD64) Windows (All)
: medium blocker
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-01-21 03:53 UTC by Florian Reisinger
Modified: 2012-01-21 16:58 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments
See description... (12.08 KB, image/jpeg)
2012-01-21 03:53 UTC, Florian Reisinger
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Florian Reisinger 2012-01-21 03:53:33 UTC
Created attachment 55900 [details]
See description...

1) Open a new Calc document
2) In cell any cell a fractin ( 3/10 ....)
3) With 3/10 it displays 03.10.12 (German DD.MM.YY)
4) Now overwrite this cell with the same fracten as in 2), but with a "=" before ( =3/10 )
overwrite...Click once on a cell and start typing
5) 30.12.99 is displayed
Please refer to the screenshot

Windows 7 x64
LibO 3.5RC1
Comment 1 Jean-Baptiste Faure 2012-01-21 16:31:32 UTC
I think it is not a bug: when you type 3/10 the first time, Calc interprets that as a date and modifies the cell format in date format. When you overwrite the contents of the cell by th formula =3/10 you have still a date, but now you have a number of day since 30/12/1899. So you get the date 30/12/1899.

Eike: can you confirm my diagnosis?

Best regards. JBF
Comment 2 Eike Rathke 2012-01-21 16:42:21 UTC
True, the once applied date format persists if a formula is entered and displays the result (taken as serial date number) as date.

First hand the confusion arises because 3/10 is accepted as date in a de-DE locale, this behavior is changed in master (to become LibO 3.6) with locale dependent date accpetance patterns, see bug 44636.
Comment 3 Eike Rathke 2012-01-21 16:58:00 UTC
And by no means this would had been a blocker bug ... closing.