Confusing date format used on localized web pages

[+LHCper]

I was checking for when I event would take place and found this:

As you maybe can see this is a localized page where my local language is used.

But the date shown is used USA style instead of localized. 

 

So I think you change this to use a better date format.

Either going for ISO standard (ie 2025/08/02).
Or making the dates localized as well.
(I believe DD/MM/YYYY is much more common globally.)

 

The same applies for example when searching for geocaches, and the list show last found and hidden dates. These are always a bit confusing for someone who are used to dd/mm(/yyyy).
To be clear we - and most of the world - do tend to write YYYY-MM-DD, as given by the ISO standard - to make things clear.
 

[+LHCper]

Here is how the list of geocaches looks like in the localized format.
So km is used instead of miles.
But for dates you need to look around to see that mm/dd/yyyy is used.

dd/mm/yyyy would be better, but yyyy-mm-dd best, according to me.

[+barefootjeff]

2 hours ago, LHCper said:

Or making the dates localized as well.
(I believe DD/MM/YYYY is much more common globally.)

 

The same applies for example when searching for geocaches, and the list show last found and hidden dates. These are always a bit confusing for someone who are used to dd/mm(/yyyy).

 

Have you set your preferred date format in your profile settings?

 

 

Mine is set to dd/mm/yyyy and cache page dates and search results all show the date in the correct format, for example this event tomorrow:

[+NLBokkie]

If only the months would be spelled out (even shortened), I think there can be no more confusion as to what date is meant. I'd like to see that as I too get confused regularly between places where the US- and other formats are used. AFAIK, the US is the only one using MM/DD/YYYY, but out of context it's pretty hard to find out if 1/2/2025 is the first day of February or the second day of January. If it shows "1 Feb 2025" or "Jan 2 2025" it's always clear which day is meant, even out of context and regardless of the date format setting chosen.

Edited September 23 by NLBokkie

[+thebruce0]

yyyy-mm-dd is universally the best choice, programmatically, intuitively, and as a compromise for all the localized formats. Honestly life would be better if everyone just used the same easy format

Yes, in some contexts (where day or month # is far more useful and valuable than the year # which may be irrelevant) it's extraneous. But in a context like this, where all 3 elements may have equal chance to be equally important, it's just simpler, imo.