> You can't assume everyone understands or expects the US date
> format. If you
> ask for a date and the user types "8/2/01", is that user giving a date in
> August or February? It depends.
>
> The same thing goes for displayed dates.
>
> Right now, if someone wants to develop a stack that works for users
> worldwide, they have to either ask the user to enter their preferred date
> format - ridiculous, since it's already available in the system settings -
> or specify, each time a date is requested or displayed, that dates must be
> MM/DD/YY. Or avoid using short dates altogether. All of this looks most
> unprofessional and unfinished in an application, apart from the annoyance
> it causes users.
I always use a method of entering the date that is understandable to all
(world wide). The method is to offer a field for day an option button for
written month and a field for year. This way there is no confustion and you
can give it a professional look. IMHO expecting the user to adhere to a your
date format is never going to look professional.
>
> If you need an invariant date format, use the English date, the
> seconds, or
> the dateItems;
Yes, I didn't actually know about the English date but it seems to return
the long date so is probably a waste of time anyway.
that's what they're there for, so you can have a
> date format
> that never changes. Assuming everyone uses the same format for displayed
> dates is asking for trouble.
Archives: http://www.mail-archive.com/[email protected]/
Info: http://www.xworlds.com/metacard/mailinglist.htm
Please send bug reports to <[EMAIL PROTECTED]>, not this list.
