https://bugs.kde.org/show_bug.cgi?id=340982

doom...@gmail.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |doom...@gmail.com

--- Comment #233 from doom...@gmail.com ---
I recently found this bug report after struggling to have suitable units and
such in a brand new Plasma install. Going through this, and then going to
upstream, has me shaking my head in disbelief.

That this regression happened a *decade* ago, and both KDE and Qt are kicking
the can back and forth at each other, is *embarrassing*. You had something that
worked previously, why even bother tying this in to a project in a way that so
thoroughly breaks user workflow??

Some people are suggesting we go upstream to get them to do something, which
strikes me as *delusional*. They clearly said in as many words that this is not
their circus and we aren't their clowns. Their suggested "solution" would be
tantamount to just rebuilding UNIX from first principles, which is a complete
non-starter.

There are some people in this comment thread suggesting that to go back to KDE
having their own locale stuff would break it in some non-KDE things. Which, I'm
sorry, I've been using linux for 20 years now, since when has KDE *ever* cared
about that?? Using KDE apps in a non-KDE environment has always been a pain in
the ass and vice versa. Why are you starting to care *now* of all times? Is
aggravating users that are neither the devs at their dev laptops nor a
hypothetical grandma non-expert user a project goal of KDE?

Either resurrect the old KDE locale methods, or issue a definitive statement
that this bug WILL NOT BE FIXED, so I know to stop wasting my time with this
project. How embarrassing is it that *Windows* has KDE beat with this?

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to