-
-
Notifications
You must be signed in to change notification settings - Fork 71
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Date format support #331
Comments
I'll work on adding localized date formats as part of #321 soon. That said, there might still be a need to add a region code selection dropdown after that, since en-US "12:00 AM" is "00:00" for en-GB for example. Or one might add their own region as a separate language in the current UI, but that could become quite chaotic since there are 91 region codes for English and 45 for French for example: https://simplelocalize.io/data/locales/ |
Is it just timestamps you're concerned with? Why not allow an option for 12hr/24hr time displays, rather than regional? |
I'm actually with @zodac on this one, despite being a US Citizen living in the US, I much prefer the 24 hour clock. Having it be a simple selection for someone to pick would be much more ideal than tying it to region IMO. |
For me it is DD/MM/YYYY that matters, I live in Denmark where we use DD/MM/YYYY for dates and not MM/DD/YYYY. 24hr is nice, it doesn't mean that much to me in a system like HomeBox, it's more the date that matters. |
I'm in Canada, and we're officially MM/DD/YYYY for a lot of things, but I also see a lot of YYYY-MM-DD, which is way more logical. Same with 24 hour - a lot of people use it preferably. Perhaps the ability to free-form customize the time/date format, similar to how you'd specify it in say PHP. |
What is the problem you are trying to solve with this feature?
There is no option to change date formats
What is the solution you are proposing?
An option to switch to a date format that suits the country in which you live.
Example: MM/DD/YYY/ to DD/MM/YYYY
What alternatives have you considered?
No response
Additional context
No response
Contributions
The text was updated successfully, but these errors were encountered: