Search results
Results from the WOW.Com Content Network
MM/DD or DD/MM does change continent wise, but the YY or YYYY remains the same for entire world (At least in countries that use English as official language). ISO 2014, though superseded, is the standard that originally introduced the all-numeric date notation in most-to-least-significant order [YYYY]-[MM]-[DD]. The ISO week numbering system ...
The problem I have with free-form entry for dates is along the lines of what Adrian mentions in his answer - the US typically does MM/DD/YYYY and other countries do DD/MM/YYYY - free-form entry makes it impossible to determine if 1/2/2010 is January 2nd or February 1st. –
It doesn't make sense to me why some people use DD/MM/YYYY or MM/DD/YYYY as we tend to put larger units at the left side, like we do with decimal numbers. When we use YYYY/MM/DD, it eases sorting and also calculating dates. It seems the global standard systems should create a unique format to prevent confusing.
For example I have spreadsheet of rows with a date column with dates in YYYY-MM-DD format. I want to transform the data, grouping by quarter, counting the rows in each quarter. The output would be something like. Q4-2017, 403 Q1-2018, 298 Q2-2018, 139 But I want to then filter down that list to only this year etc.
The short format for one or the other should NOT be used, because the US standard MM/DD/YYYY is ambigious to the "rest of the world" standard DD/MM/YYYY. This means that if the user is not aware that the date format might be different than what he expects, it is not noticed.
My intention is to guide (and not force) the users focus to those fields that are required. My example might look a bit harsh: Exchange the "x"'s with a left pointing arrow, take away the red and surround the unfilled input fields with green (while keeping the filled in fields filled green).
mm/dd/yyyy; yyyy-mm-dd; The 1st one (which has the Java pattern dd/MM/yyyy) produces 31/12/2011. I've decided that a more friendly version of this format (specifically for email notifications) is the pattern E dd MMM yyyy which produces Tue 11 Jan 2011. I need help figuring out the "email friendly" version for the other 2 versions (2nd and 3d).
Yes, consistency is important. All lower case seems (to me) to be more readable than all upper case, so I would go with dd/mm/yyyy or mm/dd/yyyy in your case (depending on the locale of your users). That said, have you considered a date picker? It's excellent for casual users who don't want to be bothered about date formats; if you keep the ...
dd/mm/yyyy hh:mm; dd/MM/yyyy HH:mm; I would imagine most people will understand what to enter for the first one whereas only a small percentage will understand the significance of the capitalized letters in the second format. As a developer I personally prefer to see the second format.
But @DanM raises a really good point that some users would take that to mean "August 8th". Since most cards tend to format their months with a leading zero, I would want to keep it. I could possibly create a JavaScript solution to achieve what you propose which would allow most people to type the month.