Details
-
Technical task
-
Resolution: Unresolved
-
P3: Somewhat important
-
None
-
None
-
-
dea91dbb5 (dev)
Description
There are various ways that CLDR supports identifying time-zones, such as the Windows identifiers (that we already could support – but don't, even on Windows, accept as IDs since they're not IANA IDs).
It would make sense to support these in a cross-platform backend (or family thereof), analogous to the existing UTC and proposed POSIX one, in addition to the (eventually std::chrono:tzdb-based but, in the mean-time) platform-specific ones.
In particular, it is possible our existing platform-specific backends support some of these names via the native APIs they call, that we should not lose when we make the transition to tzdb.
It would be perfectly reasonable for these to only be accepted via a pseudo-constructor such as QTZ::fromWindowsId() for the Windows IDs, and similar for the other types supported by CLDR.
See also QTBUG-112006's suggestions on pseudo-constructors and the constructor.
Attachments
Issue Links
- relates to
-
QTBUG-115158 Time zone names and abbreviations are not localised
- Closed
-
QTBUG-84297 QTimeZone::NameType doesn't work as documentated
- Closed
-
QTBUG-112006 Separate out POSIX zone descriptors in QTimeZone backends
- Reported
-
QTBUG-81056 Add QDateTimeFormat based on CLDR's format strings
- Open
-
QTBUG-70516 Extend Qt's support for CLDR date/time formatting
- Open
-
QTBUG-68812 A new back-end for QTimeZone based on C++20 std::chrono::tzdb
- Closed
-
QTBUG-79902 QLocale: make fuller and more faithful use of the CLDR data
- Open