-
Notifications
You must be signed in to change notification settings - Fork 184
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add and use BCP-47 time-zone identifiers in TimeZonesProvider #606
Labels
C-datetime
Component: datetime, calendars, time zones
S-medium
Size: Less than a week (larger bug fix or enhancement)
T-core
Type: Required functionality
Milestone
Comments
Blocked on #562 |
@nordzilla We plan to release 0.3 in about 3 weeks. Do you expect this to be unblocked in time for the 0.3 release, or should we punt to 0.4? |
This was referenced Aug 25, 2021
We have not documented the reasons why we need this. Here is the motivation:
A note on data size: much of the benefit of data size can be realized by using a hashing algorithm instead of the BCP47 strings. We prefer BCP47 because:
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
C-datetime
Component: datetime, calendars, time zones
S-medium
Size: Less than a week (larger bug fix or enhancement)
T-core
Type: Required functionality
Right now we are using the full IANA-style time-zone IDs from CLDR.
We would like to move toward using the BCP-47 identifiers so that we can store the time-zone IDs as TinyStrings.
Depends on
The text was updated successfully, but these errors were encountered: