Hi all,
Kohei Yoshida wrote:
...
* determining whether the input is a date without any other clues has
been (almost) proven to be error-prone, can never reach an acceptable
level, and leads to the wrath of users, largely due to localized date
formats.
So, what can we do?
The rough idea I've just come up with is to do what web applications do:
provide a date input box.
That was basically my idea, too. Though slightly different.
Aloow the user to specify, what should be interpreted as a date (and how).
E.g., IF the user specifies that dates are only strings of the form:
dd.mm.yy or dd.mm.yyyy, then only such strings would be converted to
dates (also note the *dd.mm* which is different from the American
*mm.dd* format!).
Then only such string would be converted to dates, and NOT *xx.xx*,
which would most probably be a number and NOT a date. Just my thoughts.
[This should be settable either at OOo level, or at document level.]
Sincerely,
Leonard
This way Calc also knows that the user is
about to enter a date, and try not to even parse an input as a date if
the date input box is not used or be more strict about what format is
considered a date in that scenario. That would also allow us to
localize the date format too without causing too much headache.
Other ideas are welcome.
Kohei
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
