-
Suggestion
-
Resolution: Unresolved
-
P3: Somewhat important
-
None
-
None
-
13
-
Foundation PM Prioritized
Parsing 2 digit year, for example "08", ends up being 1908. It would be useful to have possibility to set base year, for example to 2000.
- relates to
-
QTBUG-77948 Rewrite QDateTimeParser
-
- Open
-
For Gerrit Dashboard: QTBUG-46843 | ||||||
---|---|---|---|---|---|---|
# | Subject | Branch | Project | Status | CR | V |
516623,6 | QDTP: consolidate defaultValue computation and clip to range | dev | qt/qtbase | Status: MERGED | +2 | 0 |
516624,7 | QDTP: minor fixes to handling of two-digit years | dev | qt/qtbase | Status: MERGED | +2 | 0 |
516626,14 | Improve week-day-based resolution of two-digit year numbers | dev | qt/qtbase | Status: MERGED | +2 | 0 |
516882,15 | Give the caller control over the century used for two-digit dates | dev | qt/qtbase | Status: MERGED | +2 | 0 |
517426,5 | Restore ASN.1 Element tests after move to plugin | dev | qt/qtbase | Status: MERGED | +2 | 0 |
517427,8 | Adapt ASN.1 datetime parsing to use the new century control | dev | qt/qtbase | Status: MERGED | +2 | 0 |
517519,10 | Add a section on date ambiguities to QDate::fromString() | dev | qt/qtbase | Status: MERGED | +2 | 0 |
602614,2 | Let QDateTimeEdit control the century to use for two-digit years | dev | qt/qtbase | Status: MERGED | +2 | 0 |
603717,2 | Let QDateTimeEdit control the century to use for two-digit years | 6.8 | qt/qtbase | Status: MERGED | +2 | 0 |