Sure but I don’t think this ever caused an issue to anyone else…
The world could also agree to adopt the format used by most, which is YYYY/MM/DD; or the second most used one (DD/MM/YYYY) so that I won’t ever have to look at the american version ever again!
I’m pretty sure the opposite is true, someone has implemented a date entry to be always different than the default in user’s region
Microsoft is even worse, they do some places on region default, some places mm-dd-yyyy and some rare places in yyyy-mm-dd.
I remember the worst example being powershell module for exchange server and message trace log. It’d output your region’s default, but accept as input only mm-dd-yyyy
I wonder if anyone’s implemented a date entry form that changes by a regions default date format
Sure but I don’t think this ever caused an issue to anyone else…
The world could also agree to adopt the format used by most, which is YYYY/MM/DD; or the second most used one (DD/MM/YYYY) so that I won’t ever have to look at the american version ever again!
I believe it is YYYY-MM-DD actually.
I am not willing, not willing to biologically compute the distinction you imagine between ‘/‘ and ‘-‘ in this context…
https://en.m.wikipedia.org/wiki/ISO_8601
Many countries use the dd/mm/yyyy format tho? Germany, Uk, Spain…
They do, I’m just pointing to an ISO standard which most use…
I’m pretty sure the opposite is true, someone has implemented a date entry to be always different than the default in user’s region
Microsoft is even worse, they do some places on region default, some places mm-dd-yyyy and some rare places in yyyy-mm-dd. I remember the worst example being powershell module for exchange server and message trace log. It’d output your region’s default, but accept as input only mm-dd-yyyy
It shouldn’t be that hard to switch the ordering of the input fields based on information like that gleaned from the browser.