4 ms·
Certainly, and also, at second thought, having separator characters doesn't make it any less ambiguous either (DD/MM/YYYY || MM/DD/YYYY). When I said "you" I w
by izak30 19y ago
Certainly, and also, at second thought, having separator characters doesn't make it any less ambiguous either (DD/MM/YYYY || MM/DD/YYYY).
When I said "you" I was speaking for the program, my opinion is that the client should choose as well.
- edw519 19y agoThis is an old problem, but always an interesting example. I like to think I can accept almost anything from my user in a date field and know what they meant. For September 2, 2007, they should be able to type any of the following: 090207, 0902, 9/2, 9/2/7, 92. My users have also appreciated things like "T" for today, "Y" for yesterday, and of course, "" for today. The year and month should always default to the current. I could go on and on... When I saw this post, I got excited because I (like almost everyone else) have always struggled with this one. So I put in the simplest case and it couldn't handle it. Oh well.
- izak30 19y agoYeah, I agree that you should be able to do all of those examples, but if I wanted 2/9/7 to mean the same thing; there would need to be some sort of addiditional indication that I go day month year, (september second is a good example, september 13th would have been unambigious)