https://bugs.kde.org/show_bug.cgi?id=340982
--- Comment #187 from RJVB <rjvber...@gmail.com> --- (In reply to Nate Graham from comment #182) > To my knowledge, fixing this requires one of the following: > 1. Change the Qt locale system to support the feature > 2. Abandon the-in Qt locale system for this and implement a completely > custom system, like the KLocale system we had in the KDE 4 days but moved > away from in favor of QLocale > > Either one would be a huge amount of work. Isn't this exactly where OOC should make things straightforward if not easy? Just how much work would it be to clone (inherit) QLocale, merge/port the required functionality from KLocale (which I presume is or was in kdelibs4support at some point) and then (once properly debugged) do a search/replace on all the code in the frameworks, plasma and applications repositories to use the new class instead of QLocale? The amount of change could be huge, but maybe even that would be less than one might think if code using QLocale always imports qlocal.h . In that case, only that header has to be replaced with the new header, and the appropriate `using` expression. [OT] WHT happened to BKO? All of a sudden it looks as if designed for someone with a visuomotor handicap and a huge screen?! [/OT] -- You are receiving this mail because: You are watching all bug changes.
