(no title)
Hussell | 8 years ago
I can't afford to give full support to all locales (translation costs are ridiculous), so detecting and supporting the user's locale seems to be pointless unless they happen to be using one of the limited set I can give full support to (en-CA and fr-CA in my case). It seems like a far better idea to allow the user of my website to choose one of the supported locales, and see everything in the same consistent format than to have a few input widgets on each page decide to configure themselves based on the locale the browser was compiled with.
Edit: also, consider testing. Am I supposed to download a bunch of variants of Firefox to test my locale support?
jhasse|8 years ago
Even if your page isn't translated I would still want the dates to be localized. I understand English, but not the US time and date formatting.
Hussell|8 years ago
So, to do what you want, I'd have to make different versions of all the supporting documentation for each possible date format, and then get each version translated.
Also, displaying the dates the user just entered in a different format is a usability problem. (Users will complain. A lot.) So, if I did what you want, I'd likely be asked to display all dates, everywhere on the site, in the format the browser happened to be compiled with. This is possible for dates in the database, but not so much for dates in static content like news releases.
Just to be clear: I have no objection to making it easy for a website to have date input widgets which use the user's locale. I just want it to be equally easy for a website to have date input widgets in a specific locale. For example, how am I to make a website comparing date input widgets for different locales?