https://bugs.kde.org/show_bug.cgi?id=394698
--- Comment #18 from AK-47 <chkb...@safe-mail.net> --- (In reply to Nate Graham from comment #14) > See the upstream discussion in https://bugreports.qt.io/browse/QTBUG-58351. > > We had an idea to allow the user to select values/strings in the Plasma > config UI rather than locales, and then secretly set whatever locale is > mapped to it, but this ran afoul of the fact that the locales include > translated text not just string formatting. The POSIX locale system just > isn't set up to allow this to happen. So unfortunately isn't something we > can feasibly fix in KDE alone. It doesn't even seem like something that can > be done in Qt alone! Because the mapping of locales to both string > formatting and also translated text is baked into the POSIX and libc > implementation of locales, it really needs to be fixed there. > > If it's fixed at a level any higher than that, then the result would simply > be applications not respecting your formatting preferences in a > random-seeming manner. If it was done only in Qt, then all non-Qt apps would > be non-respecting, and if we did it in KDE itself (as we did in Plasma 4 and > earlier), then all non-KDE apps would be non-conforming, even those that use > Qt. It would be a matter of winning the battle but losing the war. > > So someone needs to get the ball rolling at the POSIX and libc levels to > propose a new spec, or backwards-compatible changes to the existing one. Would it be possible to create a set of custom locale files based on a system locale with the custom formats built in and "select" that one? -- You are receiving this mail because: You are watching all bug changes.
