Bug 60151 - FORMATTING: Date Formatting
Summary: FORMATTING: Date Formatting
Status: CLOSED DUPLICATE of bug 33899
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
(earliest affected) release
Hardware: Other Linux (All)
: medium normal
Assignee: Not Assigned
Whiteboard: BSA
Depends on:
Reported: 2013-02-01 10:54 UTC by Graeme Gemmill
Modified: 2013-03-07 00:28 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Note You need to log in before you can comment on or make changes to this bug.
Description Graeme Gemmill 2013-02-01 10:54:19 UTC
Problem description: 
Cell is formatted for dates dd/mm/yy. When I try to enter today's date (1st February) as 1/2/13, as soon as the fourth character (the second /) is typed, the first three are interpreted as 1/2, so the contents become ½/2013

Steps to reproduce:
1. Set English style date format
2. Format a cell for 31/12/99 type date
3. type 1/2/2013

Current behavior:
Expected behavior:
Operating System: Linux (Other)
Version: release
Comment 1 Jorendc 2013-02-01 11:28:51 UTC
I can confirm this behavior when I set Cell language as 'English (VS)' using LibreOffice Linux Mint 14 x64. But I'm not sure this is a bug, or correct behavior. Because you choose to set a data field with formatting MM/DD/YY...

@Markus: can you confirm this is a bug or this is correct behavior?
Comment 2 Markus Mohrhard 2013-02-13 17:49:57 UTC
Number format code and date pattern detection is Eike's area.
Comment 3 Eike Rathke 2013-02-13 22:50:55 UTC
Well, yes, but this is not a number formatter/scanner problem ;-)

It is auto-correction that hits first and then the "corrected" string is fed to the scanner that of course shakes head ...

The workaround is to disable under Tools->AutoCorrectOptions the entries for 1/2, 1/4 and 3/4

The proper cure would be that these specific entries are not to be triggered if another '/' slash followed. AFAIK that's somewhere in the EditEngine.
Comment 4 Eike Rathke 2013-03-07 00:27:57 UTC

*** This bug has been marked as a duplicate of bug 33899 ***