You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Main use-case is better presentation of timezones to users and support for timezone selection done by users.
CLDR describes other variants of timezone names like BCP47-identifiers ("uslax" for "America/Los_Angeles" etc.), regional formats ("Los Angeles Time" or "Italy Time") and the extra pattern symbol "V" (count 1 => BCP47 id, count 2 => tzid (IANA format, actually supported by Time4J), count 3 => exemplar city and count 4 => regional format). All the underlying data are missing in Java and Android.
A better support is possible based on an extra tz name repository which could be integrated into the olson-module. Without this, the fallbacks described in CLDR could be used and might even apply for Java 6+7 and Android, see also:
Main use-case is better presentation of timezones to users and support for timezone selection done by users.
CLDR describes other variants of timezone names like BCP47-identifiers ("uslax" for "America/Los_Angeles" etc.), regional formats ("Los Angeles Time" or "Italy Time") and the extra pattern symbol "V" (count 1 => BCP47 id, count 2 => tzid (IANA format, actually supported by Time4J), count 3 => exemplar city and count 4 => regional format). All the underlying data are missing in Java and Android.
A better support is possible based on an extra tz name repository which could be integrated into the olson-module. Without this, the fallbacks described in CLDR could be used and might even apply for Java 6+7 and Android, see also:
The text was updated successfully, but these errors were encountered: