I don’t want my date-time representation to change per the country I’m in; I want to be able to choose between specific standards, such as RFC 3339 or ISO 8601, the latter being my preference.
I am easily able to do so on Windows, but don’t appear to be able to do so in the regional settings KCM. Is this possible?
PS /home/rokejulianlockhart> who -b
system boot 2023-05-21 18:09
PS /home/rokejulianlockhart> date
Sun 21 May 22:33:47 BST 2023
Yeah.
Thanks for your assistance, @Duha – I’ll probably just file an FR at bugs.kde.org rather than potentially corrupt configuration files, since that wouldn’t do any less technically competent users any good (and Plasma should have at least feature parity with Windows).
Sure, and that works fine in a single app. But do you really want to re-define your favorite date format in every single app? Probably not. Which is why it needs to be done centrally, in one place, in a way that all apps that ask for date formats can consume. Which is a lot harder, because the POSIX data standard currently does not easily support defining arbitrary date formats.
In KDE 4 times, we let you define arbitrary custom date formats, bypassing the POSIX locale standard, but it only worked for KDE apps that specifically knew how to read the KDE-defined date format. So people complained that GNOME and other apps didn’t get the same date formatting, and there was no way to fix this issue in principle because we were explicitly ignoring the cross-desktop standard and the GNOME folks (to say nothing of all other software) weren’t going to adopt the KDE thing as a new de-facto cross-desktop standard to replace the existing one. So, in Plasma 5 times, we admitted defeat and went back to supporting POSIX locales so now the format you choose applies to all apps. But as a consequence, you can’t arbitrarily customize the date format.
Those are the limitations and external conditions involved.
Idk, maybe its just me, but I was hoping for a more modern standard and using posix just as a fallback if the more modern standard is not available.
Posix: Latest version IEEE Std 1003.1-2017
2017; 6 years ago
(Most) modern Linux Distris already embrace modern technology like systemd, wayland etc…, who knows what the BSD’s and a few small Distris will do? Maybe I’m just naive, but I wish we would move on from projects that want to stay in 1980.
was a retrograde step, as I’m sure the developers who had to choose this path thought too. I don’t mind having to set two similar preferences – we already have the ability to choose a different GTK theme preference. Where it’s necessary, I think that the “Powerful when needed” part of the KDE mantra applies here.
To restate this more broadly, since from the response at id=480683#c3 I don’t believe that this is adequately appreciated, I’ve created gitlab.com/-/snippets/4823517:
The Current State of Standard Adherence in the Stead of Retrograde “Locale” Norms (in OSes and DEs)
plasma-systemsettings-6.3.2-1.fc41.x86_64
In kcm_regionandlang, I see options to set locales for a multitude of options:
For each of these, a standard corresponds that I want to prefer, yet which is unavailable in most or all locales:
This isn’t acceptable, for the massive difference in information formatting and density in comparison to what is internationally accepted, and more importantly, what I work with every day, is stark. windows.immersivecontrolpanel_10.0.8.1000 provides options to get a damn lot closer than this. I’d rather have KDE’s applications adhere to my preferences and have these as a fallback then aim for the lowest common denominator.
windows.immersivecontrolpanel_10.0.8.1000 and intl.cpl in OsBuildNumber: 26120[11]
ms-settings:regionformatting[12] of windows.immersivecontrolpanel_10.0.8.1000 is very disappointing in comparison to kcm_regionandlang’s GUI and intl.cpl’s functionality, but does provide standard format choices:
intl.cpl is damned perfect in comparison:
Additionally, although tangentially related, I’m seriously impressed that these configurations can even be set as the defaults for new users of the OS!
It is BSD. macOS, like AOSP+GMS, is a customised distribution of Darwin, which uses the XNU kernel. That kernel is solely compatible with a BSD base. Darwin is an amalgamation of NeXTSTEP and freeBSD, with very occasional GNU binaries.
I meant that, it’s possibly the case that, macOS has implemented the system time format feature simply because, they’re Apple – independent of whether or not BSD makes it easier to offer such features or, not.
Regardless, thanks for the investigation – I’ve long suspected that, a UNIX® certification is quite costly and, there’s sufficient evidence showing that, that’s the only reason that, Linux ain’t a certified UNIX®.
BTW, my first contact with a UNIX® was the DEC ULTRIX OS, which was a BSD UNIX® because, DEC and AT&T had a difference of opinion back in the late 1970’s – despite UNIX® as such being initially only available for DEC PDP-11 (16-bit) hardware.