GitLab team member here.
You can use absolute times (ex: October 14, 2023 11:51AM) instead of relative times in GitLab by changing your preferences: https://docs.gitlab.com/ee/user/profile/preferences.html#sho...
You can use absolute times (ex: October 14, 2023 11:51AM) instead of relative times in GitLab by changing your preferences: https://docs.gitlab.com/ee/user/profile/preferences.html#sho...
Not only on GitLab, but everywhere. In any application. On any website. It's a pain in the ass on Linux.
C.UTF-8, but you are correct. Windows solved this years ago.
I must be misunderstanding you.
I can't get ISO-8601 dates to work properly in Excel unless I set my Windows to Australia locale, or make my own parser or use a third-party library.
Sure, I can format a field^Wcell with a custom format string, but Excel still won't believe me when I type/paste/import ISO-8601 dates. Unless I set 'Australia' systemwide.
And no, simply adding English (Australia) as one of the additional system languages, or keyboard layouts (and switching to that layout), or number+date+currency formats doesn't work.
But you could also customize the region settings in "Additional settings...".
Setting locale to `en_SOMEEUROPEANCOUNTRY` will make some programs use ISO 8601 dates everywhere, but other programs use all sorts of random formats. Switching between countries changes what different subsets of programs do.
Instead of providing a useful meaningful date, you:
- obscure information
- spent additional devtime creating a time conversion
- spent additional time implementing an otherwise useless setting for this
Why?!