[Libreoffice-bugs] [Bug 52240] [Task] EDITING: Incomplete Date values are no longer detected

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=52240

Eike Rathke <erack at redhat.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
     Ever Confirmed|0                           |1

--- Comment #7 from Eike Rathke <erack at redhat.com> 2012-07-20 15:20:59 PDT ---
(In reply to comment #0)
> 1-7 --> 1.7.2012
> 1-7-12 --> 1.7.2012
> 1.7 --> 1.7.2012
> 1.7.12 --> 1.7.2012
> 
> This behaviour is no longer present. It's now necessary to enter "1.7.2012" all
> the time, which takes a long time when you have large tables to edit...

Indeed we missed to add a date acceptance pattern for de_AT abbreviated dates.
However, I think that then should be D.M. and not D.M (note the trailing dot
difference), people from German language regions actually were complaining
about the recognition of 1.7 as date instead of string, e.g. as in a numbering,
therefor input of 1.7. would be necessary for date recognition.

For 1-7 case it's similar, it may easily get in your way.

For 1-7-12 there's the dreaded interference with ISO 8601 abbreviated dates
(though we could say that for these the year has to be >31, but will users
understand that?)

Btw, 1.7.12 _is_ accepted and leads to 1.7.2012

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.