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). ------------- Commit messages: - init Changes: https://git.openjdk.org/jdk/pull/33074/files Webrev: https://webrevs.openjdk.org/?repo=jdk&pr=33074&range=00 Issue: https://bugs.openjdk.org/browse/JDK-8392995 Stats: 155 lines in 3 files changed: 151 ins; 0 del; 4 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
