-
Enhancement
-
Resolution: Not an Issue
-
P4
-
None
-
None
-
generic
-
generic
Currently in java.util.TimeZone a user can call TimeZone.getAvailableIDs() which returns 600+ identifiers at the moment. Although all the results are technically valid, the results contain the deprecated 3-letter Java identifiers, as well as historical tzdb identifiers that exist for compatibility reasons, which are ultimately mapped to a modern identifier. For example, 'Japan' is mapped to 'Asia/Tokyo' (Pre-1993 naming conventions), 'Mexico/General' is mapped to 'America/Mexico_City' (Pre-2013 practice), etc.
For users without compatibility concerns, they should be encouraged to use modern tzdb identifiers in their applications.
This issue proposes adding the static method getModernIdentifier(String ID) which takes an identifier, and returns the modern equivalent if applicable, otherwise it returns the input ID.
For users without compatibility concerns, they should be encouraged to use modern tzdb identifiers in their applications.
This issue proposes adding the static method getModernIdentifier(String ID) which takes an identifier, and returns the modern equivalent if applicable, otherwise it returns the input ID.
- csr for
-
JDK-8311960 Introduce method in TimeZone to provide modern identifier name
-
- Closed
-