To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=104504


User berglundma changed the following:

                What    |Old value                 |New value
================================================================================
              Issue type|DEFECT                    |ENHANCEMENT
--------------------------------------------------------------------------------




------- Additional comments from berglun...@openoffice.org Wed Aug 26 13:02:52 
+0000 2009 -------
Clearly at this point we are into opinion, but I suggest that because there is a
pattern being specified in the controls format selection, this expectation is
not unresonable. 

As you pointed out, 02/02/2002 could be represented by 02022002 or 020202 except
that there is a difference in the accepted format between the two. There is a
format for 02/02/2002 and 02/02/02, and they are different. In each case an
intelligent decision can be made. It would also be possible for a regional
setting to make sense of reasonable input, respecting the various global
expectations for these sorts of formats. From a programmatic prospective I
understand the need to minimize code and not arbitrarily predict input, but I
also know that we really need to allow for the end user as well, and I'm not
sure that we're doing that.

I agree, this idea doesn't stop with 24 hour times. I'm sure that we can find a
number of other places where input styles (dates) can be improved and made more
intelligent. For the user, sure, it is magic! And (for them) it just works(tm).

Implementing a Pattern field makes sense for something for which we do *not*
have a predefined format. In this case we have pre-defined formatting for many
number styles (currency, times, dates, scientific notation, etc.) and yes, I
suggest that there are regionally understood shorthands for which the computer
can, and should, compensate. 

At the risk of being redundant, I see _not_ doing things like this as making
data entry pedantic for OOo. I think this fundamentally changes the usability of
OOo for end users, especially when compared to other experiences.
 
I very much appreciate your time and our discussion. Your insight has been
valuable to me. I have moved this to enhancement.

---------------------------------------------------------------------
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@dba.openoffice.org
For additional commands, e-mail: issues-h...@dba.openoffice.org


---------------------------------------------------------------------
To unsubscribe, e-mail: allbugs-unsubscr...@openoffice.org
For additional commands, e-mail: allbugs-h...@openoffice.org

Reply via email to