date: refer to tzdata as a 'distribution' rather than 'package'

[kevans]

Summary

This is perhaps a bit pedantic, but one could misunderstand the use of
'package' here to mean a package provided by pkg, rather than the fact
that we use the distributable package provided by the tzdata project.

Sponsored by: Klara, Inc.

[pauamma_gundo.com]

I agree "package" is unclear, but I have mixed feelings about "distribution". "tzdata data" read weirdly to me, so what about "information"?

[rpokala]

In D35966#816520, @pauamma wrote:

I agree "package" is unclear, but I have mixed feelings about "distribution". "tzdata data" read weirdly to me, so what about "information"?

"tzdata files"?

(But I think "tzdata distribution" is fine.)

[philip]

The maintainers of the time zone database consistently use the term "database" to refer to the data. The term "distribution" in the tz context refers exclusively to the tarballs (tzcode, tzdata and tzdb).

I would suggest using database in preference to package or distribution too. I agree that package is ambiguous.

Something like this could work:

which contains the time zone definitions from the IANA Time Zone Database
.Sy (tzdata) .

Or:

...Time Zone Database
.Sy tzdata ,
distributed by IANA.

Or something along those lines.

[kevans]

Change course, expand tzdata to "IANA Time Zone Database (tzdata)" on first use,
then just call it "tzdata" in later references without trying to call it a
distribution or package.

[philip]

Good compromise! Thank you.