-
Notifications
You must be signed in to change notification settings - Fork 5.8k
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
8340073: Support "%z" time zone abbreviation format in TZ files #20979
Conversation
👋 Welcome back naoto! A progress list of the required criteria for merging this PR into |
@naotoj This change now passes all automated pre-integration checks. ℹ️ This project also has non-automated pre-integration requirements. Please see the file CONTRIBUTING.md for details. After integration, the commit message for the final commit will be:
You can use pull request commands such as /summary, /contributor and /issue to adjust it as needed. At the time when this comment was updated there had been 52 new commits pushed to the
As there are no conflicts, your changes will automatically be rebased on top of these commits when integrating. If you prefer to avoid this automatic rebasing, please check the documentation for the /integrate command for further details. ➡️ To integrate this PR with the above commit message to the |
/label remove build |
@naotoj |
Webrevs
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
IIUC we treat the %z FORMAT the same as the numeric offset FORMAT, that is we rely on the STDOFF to calculate the GMT format during runtime.
The changes in convertGMTName(String f)
seem to accomplish that.
LocaleResources lr = LocaleProviderAdapter.forType(Type.CLDR).getLocaleResources(l); | ||
ResourceBundle fd = lr.getJavaTimeFormatData(); | ||
var zi = ZoneInfoFile.getZoneInfo(id); | ||
if (zi == null) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is an added fallback, and is not related to the "%z" logic right?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Right. Since getZoneInfo()
could return null
, this is just for safety.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Thanks for the reviews! |
Going to push as commit 418bb42.
Your commit was automatically rebased without conflicts. |
Yet another preparation for upgrading the time zone data to 2024b, which introduced a new abbreviation format "%z". The update includes:
...
The main source files' time zone abbreviations now use %z,
supported by zic since release 2015f and used in vanguard form
since release 2022b. For example, America/Sao_Paulo now contains
the zone continuation line "-3:00 Brazil %z", which is less error
prone than the old "-3:00 Brazil -03/-02". This does not change
the represented data: the generated TZif files are unchanged.
Rearguard form still avoids %z, to support obsolescent parsers.
...
Also fixed the logic to retrieve the linked tz name that is chaining.
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/20979/head:pull/20979
$ git checkout pull/20979
Update a local copy of the PR:
$ git checkout pull/20979
$ git pull https://git.openjdk.org/jdk.git pull/20979/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 20979
View PR using the GUI difftool:
$ git pr show -t 20979
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/20979.diff
Webrev
Link to Webrev Comment