> This PR corrects a case when the explicit DST offset metazone mapping is used > by `SimpleDateFormat` even when a custom time zone is active. > > For example, one can create a custom time zone named "America/Vancouver" that > has no daylight time. The code before this fix would attempt to match the > custom zones total offset to the CLDR metazone dstoffset to determine > daylight time. > > Such custom zones should not consult the metazone dstoffset mapping to > determine their daylight naming. Note that it is fine for custom names to be > used with a standard zone and still go through the metazone mapping. > > --------- > - [x] I confirm that I make this contribution in accordance with the [OpenJDK > Interim AI Policy](https://openjdk.org/legal/ai).
Justin Lu has updated the pull request incrementally with one additional commit since the last revision: Reflect review comments (replace isDirty and hasSameRules for equals) + simplify modified zone test a little ------------- Changes: - all: https://git.openjdk.org/jdk/pull/33074/files - new: https://git.openjdk.org/jdk/pull/33074/files/5cbbbafc..12ac355c Webrevs: - full: https://webrevs.openjdk.org/?repo=jdk&pr=33074&range=01 - incr: https://webrevs.openjdk.org/?repo=jdk&pr=33074&range=00-01 Stats: 32 lines in 2 files changed: 5 ins; 2 del; 25 mod Patch: https://git.openjdk.org/jdk/pull/33074.diff Fetch: git fetch https://git.openjdk.org/jdk.git pull/33074/head:pull/33074 PR: https://git.openjdk.org/jdk/pull/33074
