On Mon, Sep 26, 2011 at 05:45:30PM +0100, Zefram wrote:
> Dave Rolsky wrote:
> > That information isn't easily accessible on a system in any other
> >way that I know of.
>
> It's supplied in data structures in T:OTZ:D or DT:TZ:Olson. Including the
> parts that aren't represented in the old DT:TZ:Catalog data structures.
> As I said earlier, it's easy to write code around that to present it
> as POD, or in any other human-oriented format. We could provide a
> command-line program that wraps that. How easy does it have to be?
>
> I'd be interested to hear from people who actually use the current
> DT:TZ:Catalog document.
I use the DateTime::TimeZone::Catalog, as an easy reference so I can see
what zones I have installed *on this box*, as opposed to wikipedia-type
references that list the various timezones that exist (that may or may not
be installed locally, depending on the age of my data).
Perl documentation should be available via 'perldoc'. A pod that simply
says "run this command to see all installed zones: ..." is fine - just
don't take away easy access to my installed zones, or the
DateTime::TimeZone::Catalog pod.
So, if you're not going to generate a pod that contains this list at build-
or install-time, please provide an executable (App::Cmd is nice!) that
generates the list on the fly.
--
"Martyrdom has always been a proof of the intensity,
never of the correctness, of a belief." - Arthur Schnitzler
. . . . .
Karen Etheridge, [email protected] GCS C+++$ USL+++$ P+++$ w--- M++
