Details
-
Bug
-
Resolution: Fixed
-
P2: Important
-
5.7, 6.6, 6.7
-
None
-
-
21
-
58fd829cd (dev), c8b70f4e5 (dev), 0f770b0b3 (dev), 4017bc5ad (dev), 43cb4136a (dev), a7338bd83 (6.7), 249b8ff3f (6.7), af4bccb56 (6.7), 5f8dc8ea5 (dev), e8d20b145 (tqtc/lts-6.5), 67753fa39 (tqtc/lts-6.5), ec1631c48 (tqtc/lts-6.5), bd01008bc (dev)
-
Foundation Sprint 91, Foundation Sprint 92, Foundation Sprint 93, Foundations Sprint 94, Foundations Sprint 95, Foundations Sprint 96, Foundations Sprint 97, Foundations Sprint 98, Foundations Sprint 99, Foundation Sprint 100, Foundation Sprint 101, Foundations Sprint 102, Foundation Sprint 103, Foundation Sprint 104, Foundation Sprint 105, Foundation Sprint 106, Foundation Sprint 107, Foundation Sprint 108, Foundation Sprint 109, Foundation Sprint 110, Foundation Sprint 111, Foundation Sprint 112, Foundation Sprint 113, Foundation Sprint 114, Foundation Sprint 115
Description
QDateTime::timeZoneAbbreviation() and QTimeZone::abbreviation() make no attempt at localization. They end up using the C locale (in effect) for UTC and UTC-offset time representations but a system-supplied (hence typically the system locale's form of) the names and abbreviations for local time or a time zone. When QLocale::toString() is given a format that includes the time zone, it thus fails to correctly reflect the locale that was asked to represent it.
Attachments
Issue Links
- is duplicated by
-
QTBUG-122448 Date().toLoacleTimeString() doesn't respect the locale
- Closed
- relates to
-
QTBUG-84297 QTimeZone::NameType doesn't work as documentated
- Closed
-
QTBUG-124271 Repeatedly calling QLocale::toString with timezone is slower than it should be
- Open
-
QTBUG-112909 Support all CLDR's various ways of naming time-zones
- Open
-
QTBUG-68812 A new back-end for QTimeZone based on C++20 std::chrono::tzdb
- Closed
- resulted in
-
QTBUG-114914 Using QLocale to set it to English will also display Chinese
- Closed