https://bugs.kde.org/show_bug.cgi?id=340982
--- Comment #184 from Smittie <bugs....@smittieandcompany.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. > > I wasn't around for the KDE 4 days, but if I had been, I probably would have > been against abandoning KLocale (which could do this) for QLocale (which > can't). That switch also introduced Bug 394698, which is the other major > annoyance with this KCM. > > So in retrospect I personally think that switch may have been a mistake, but > what's done is done. Hopefully we can learn from that mistake and do better > in the future. Since fixing this is not a trivial task, it will probably > take a while and require a senior developer. Then (as cat22 noted in comment #181) this should be the explanation in the *CLOSED - WILL NOT FIX* resolution. It's ridiculous that this bug sits open with no intent to fix it. -- You are receiving this mail because: You are watching all bug changes.
