https://bugs.kde.org/show_bug.cgi?id=345378
--- Comment #41 from Jan Ziak (http://atom-symbol.net) <0xe2.0x9a.0...@gmail.com> --- (In reply to Martin Klapetek from comment #40) > (In reply to Jan Ziak (http://atom-symbol.net) from comment #38) > > (In reply to Martin Klapetek from comment #1) > > > This is available in the "Formats" system settings module. Due to the > > > nature > > > of the underlying technology, we cannot offer anything better at this > > > point. > > > > What does "nature of the underlying technology" mean exactly? > > As explained in my comments above, we have switched > from what you presumably link in your screenshots to > Qt's solution, which was set to contain all the features > you want, but so far it doesn't. > > Also as noted above, KDE is fully aware of this issue > and we are fully aware what the options were before, > you don't need to link them to us, really. At this point > it's a resources problem, projects are understaffed and > more pressing issues are being worked on. > > Finally, the solution is NOT easy. This WILL have to > go into Qt itself and that means support for all the > platforms Qt supports, which is incredibly complicated > and also partly the reason why it's not done yet. > > That said, no need to comment on this further, we know > about this issue and there's nothing that we're able do > about this for now, sorry. Simply adding the same comments > over and over won't magically solve it. I don't understand your reply. In either case, I don't see it as an issue anymore: I patched the underlying Qt code (qlocale.cpp, Gentoo) on my machines. The patch simply modifies QLocale::dateFormat(FormatType)→QString and returns the format string I prefer to use (such as "yyyy-MMM-dd"). I guess I could have also used LD_PRELOAD to modify the behavior of function QLocale::dateFormat(FormatType), but that wouldn't cover the case of compiler inlining the function (within qlocale.cpp, or in case of -flto). -- You are receiving this mail because: You are watching all bug changes.
