Hacker News Reader

Comment by Yaggo | Hacker News Reader

Nice, but why <input type="date"> expects U.S. format 'mm/dd/yyyy' instead of native format used in my system?

If it falls back to default format, at least the default could little bit more universal/stanard, e.g. 'yyyy-mm-dd'.

Edit: Even after switching my preferred language from English to Finnish in browser settings, the format stays 'mm/dd/yyyy'. I'm using Finnish region in my OS settings as well.

View on HN

Many english speakers use en_US by default since it's the thing that breaks the least, so using the native format of the system is not useful. It should use ISO-8601 (yyyy-mm-dd) unless someone explicitly sets it in about:preferences.

> Many english speakers use en_US by default since it's the thing that breaks the least, so using the native format of the system is not useful.

Sorry, I'm not following you. Every application should use the format defined in OS settings, that's the point of the system setting, why should browser be an exception?

Most people intentionally set their locale wrong, to en_US, because a lot of apps simply do not have actual locale support, but try to do something when presented with a non-en_US locale.

I know many like me, who also just prefers the application language to be in English. From decades of using English I have no idea what many terms are in my native language, native terms are much harder to google, and many applications are also poorly translated. But that doesn't mean I want everything in English, especially not date/time formats.

Language and locale (how you want your date or numbers formatted) are two different things. You can set them separately.

I can set them, all right. Somebody else then needs to read them, though...and has to take care not to assume that LANG===LC_TIME===LC_DATE. Sadly, I do not see that happening; in most cases, the apps are picking one locale setting, seemingly at random, and using it for all the other locale settings.

I cannot remember an app that did not support dd/mm/yyyy format. It is the first thing a non-US English speaker will complain about.

Last time I used Peoplesoft it had everything in American date format.

dd/mm/yyyy is indeed what I'll complain about: that's as unclear as possible. Did the author mean dd.mm.yyyy or mm/dd/yyyy?

DD/MM/YYYY is more widely used than the US-only MM/DD/YYYY. Ultimately, ISO 8061 (YYYY-MM-DD) is the only really usable one.

Nope, you're thinking of DD.MM.YYYY - using the USian separators with the European date ordering is a recipe for trouble. Agree on the ISO form.

We use DD/MM/YYYY in Australia. I can definitely agree that it adds to the confusion. ;)

That's the reason to use en_GB locale instead. European date and time formats and English language for the UI. Rarely if ever saw anything broken.

Yes I try to do that but I sometimes have used (accidentally) en_US in the past since I use ANSI International keyboard layout but GB locale settings.

Agreed. ISO-8601 is the way to go.

Didn't you know? There does not exist a world outside the US. We're all just illusions and bots.

In the German localization it's correctly displayed as 'dd.mm.yyyy'. Other formats are possible but not yet enabled for every language, it seems.

Weird, given that ´new Intl.DateTimeFormat('fi-FI').format(new Date)´ in console properly outputs dd.mm.yyyy, so the locale data for Finnish should be there.

It uses the locale of your Firefox install (which you can select when you download the browser). This isn't configurable within an install (yet).

I hope the plan is to read the configured date format on the system like most software out there? This really shouldn't need to be manually configured.

Works on Android though (or does the Play Stpre download a localized version for me?).

IIRC it does

Reply on news.ycombinator.com