Commitdb692b0

committed

Doc: improve timezone/README's recipe for tracking Windows zones.

We should now cite CLDR as primary reference for the zone namemapping.Discussion:https://postgr.es/m/3266414.1633045628@sss.pgh.pa.us

1 parente54a758 commitdb692b0Copy full SHA for db692b0

File tree

+11

-5

lines changed

+11

-5

lines changed

Lines changed: 11 additions & 5 deletions

Original file line number	Diff line number	Diff line change
`@@ -45,11 +45,17 @@ and pg_timezone_abbrevs views don't throw errors). It's worth running it`
`45`	`45`	`as a cross-check on proposed updates.`
`46`	`46`
`47`	`47`	`When there has been a new release of Windows (probably including Service`
`48`		`-Packs), the list of matching timezones need to be updated. Run the`
`49`		`-script in src/tools/win32tzlist.pl on a Windows machine running this new`
`50`		`-release and apply any new timezones that it detects. Never remove any`
`51`		`-mappings in case they are removed in Windows, since we still need to`
`52`		`-match properly on the old version.`
	`48`	`+Packs), findtimezone.c's mapping from Windows zones to IANA zones may`
	`49`	`+need to be updated. We have two approaches to doing this:`
	`50`	`+1. Consult the CLDR project's windowsZones.xml file, and add any zones`
	`51`	`+ listed there that we don't have. Use their "territory=001" mapping`
	`52`	`+ if there's more than one IANA zone listed.`
	`53`	`+2. Run the script in src/tools/win32tzlist.pl on a Windows machine`
	`54`	`+ running the new release, and add any new timezones that it detects.`
	`55`	`+ (This is not a full substitute for #1, though, as win32tzlist.pl`
	`56`	`+ can't tell you which IANA zone to map to.)`
	`57`	`+In either case, never remove any zone names that have disappeared from`
	`58`	`+Windows, since we still need to match properly on older versions.`
`53`	`59`
`54`	`60`
`55`	`61`	`Time Zone code`

Comments

(0)