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

Nate Graham <[email protected]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           See Also|                            |https://bugreports.qt.io/br
                   |                            |owse/QTBUG-122216,
                   |                            |https://bugreports.qt.io/br
                   |                            |owse/QTBUG-58351,
                   |                            |https://bugreports.qt.io/br
                   |                            |owse/QTBUG-17107,
                   |                            |https://bugreports.qt.io/br
                   |                            |owse/QTBUG-122633
            Summary|No way to change the        |Re-add ability to customize
                   |systemwide date and time    |time/date/formats/etc. in a
                   |formats but not their       |granular way
                   |actual translated text      |
         Resolution|UPSTREAM                    |---
                URL|https://bugreports.qt.io/br |
                   |owse/QTBUG-58351            |
             Status|CLOSED                      |REOPENED
           Severity|normal                      |wishlist

--- Comment #299 from Nate Graham <[email protected]> ---
To fix this "properly", I think KDE would need to create a UI for people to
customize their formats that would create a glibc locale under the hood, and
then Qt folks would need to re-do QLocale to use glibc locales directly, so
that all Qt-based software would use the custom locale that you created with
the KDE UI.

However it's not clear to me from the Qt bug reports that the Qt folks even
want that; they seem interested in remaining with the existing CLDR and
ICU-based implementation, which implies that no upstream fix is actually
possible here.

Given that…

(In reply to Kevin Kofler from comment #284)
> * Considering that users are expecting features that KLocale provided and
> that neither QLocale (Qt/ICU locales) nor POSIX/glibc locales are able to
> provide, it should be obvious that deprecating KLocale was a mistake and
> that it needs to be resurrected *now*. This issue report has 133 users on
> the CC list, 19 duplicates, and 283 comments. This makes it clear that this
> is a priority for your users.
At this point I think it's worth considering. The challenge is that it would be
a ridiculous amount of work.

Maybe we could reach out to the Qt folks to see if there are any small changes
to QLocale they'd be willing to accept so we don't have to port away from it.
Like maybe there could be an optional "only use glibc locales" mode to unblock
a custom glibc locale creation UI. Or a way to create custom Qt-specific
locales so at least we could create custom locales that would work in all KDE
and Qt apps.

Re-opening, and marking as a wishlist.

Please try to keep the non-technical chatter to a minimum. :)

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

Reply via email to