Problem description: Used to be able to input dates in date formatted cells using a dash, eg 08-12 would be Aug 12 (we're using the YYYY-MM-DD ISO format, so this makes sense for our use case). Calc doesn't recognise 08-12 as something that should be formatted as a date. Now I must use a forward slash instead, eg 08/12, which calc formats as a data (in my case, 08/12 becomes 2012-08-12). Steps to reproduce: 1. Create/open spreadsheet 2. Format a date cell 3. Profix Platform (if different from the browser): Win7 x64 Browser: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:14.0) Gecko/20100101 Firefox/14.0.1
IMHO ISO 8601:2004 does not allow MM-DD, so that might be intended. On the other hand we need some easy to handle auto recognition also for ISO More or less DUP of / related to "Bug 52288 - [DE] EDITING: Allow truncated date inputs from numeric keyboard" "Bug 52240 - [Task] EDITING: Incomplete Date values are no longer detected" @Daniel Deboer: Please contribute info concerning your localization settings @Eike: One more for the fine tuning of date recognition For me a MM-DD input still would be the most preferred solution, for my sake with an option "Activate ISO-like MM-DD short input. For me that also would be an acceptable solution for Bug 52288
LO Localisation is: Default - English (USA) Win7 Regional settings: English (United States)
(In reply to comment #1) > IMHO ISO 8601:2004 does not allow MM-DD, so that might be intended. On the > other hand we need some easy to handle auto recognition also for ISO > > More or less DUP of / related to > "Bug 52288 - [DE] EDITING: Allow truncated date inputs from numeric keyboard" > "Bug 52240 - [Task] EDITING: Incomplete Date values are no longer detected" > > @Daniel Deboer: > Please contribute info concerning your localization settings > > @Eike: > One more for the fine tuning of date recognition > For me a MM-DD input still would be the most preferred solution, for my sake > with an option "Activate ISO-like MM-DD short input. For me that also would be > an acceptable solution for Bug 52288 Just to be clear, LO recognised MM-DD in the 3.5 release, so this has changed in 3.6. Also this is a problem for all date formats, not just YYYY-MM-DD. If I format a cell with any date format and enter 08-12 or 8-12 or anything with a dash, LO doesn't recognise this as a date and apply formatting.
@Daniel: That's all known, currently no further information is reequired.
(In reply to comment #1) > IMHO ISO 8601:2004 does not allow MM-DD, so that might be intended. Indeed MM-DD is not among the various ISO 8601 representations. > One more for the fine tuning of date recognition > For me a MM-DD input still would be the most preferred solution, for my sake > with an option "Activate ISO-like MM-DD short input. For me that also would be > an acceptable solution for Bug 52288 I'd rather introduce a general "edit date acceptance patterns" field than have yet another option that serves just one specific purpose. And may be misleading for locales that use Y-M-D with M-D abbreviation anyway.
> I'd rather introduce a general "edit date acceptance patterns" field Yes, such a user-individual possibility sounds very promising. Can you consider in your thoughts that for some people an "Input only day" possibility is rather important? For example for accountancies or project flow planning I often have to input lots of lots of dates, most for a time today +- 2 weeks, into a list of prepared contents. For such it's significant extra work if you have to add day + month instead of only day (for 90% of the entries).
** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present on a currently supported version of LibreOffice (4.3.5 or later): https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) Thank you for your help! -- The LibreOffice QA Team
Works for me now, Windows 7, LO 4.3.4.1