> On Wed, Sep 24, 2003 at 10:54:04AM -0500, Dave Rolsky said:
> > You do realize that mapping time zones to countries will take a _lot_ of
> > maintenance, right?
>
> Just as a FWIW ...
>
>
http://blogs.gotdotnet.com/raymondc/PermaLink.aspx/8b23d26b-7e11-425d-b612-13396ef3ec71
It's good to keep th
> Wouldn't the major city names be less prone to these kinds of disputes?
> Surely there will be times when some will be disputed but I don't see
> it happening so often as to be a major problem.
This is what the Olson DB does.
> Lastly, I'm for some reason or another not worried if people like t
> You do realize that mapping time zones to countries will take a _lot_ of
> maintenance, right?
I agree completely. I don't know many different ways it has to be stated before the
maintenance issues are taken seriously.
> Countries are changing all the time. Think back to the end of the cold
On Wed, 24 Sep 2003, Michael Fair wrote:
> Wouldn't the major city names be less prone to these kinds of disputes?
> Surely there will be times when some will be disputed but I don't see
> it happening so often as to be a major problem.
Yeah, that's why the Olson DB uses continents and cities onl
On Wed, Sep 24, 2003 at 10:54:04AM -0500, Dave Rolsky said:
> You do realize that mapping time zones to countries will take a _lot_ of
> maintenance, right?
Just as a FWIW ...
http://blogs.gotdotnet.com/raymondc/PermaLink.aspx/8b23d26b-7e11-425d-b612-13396ef3ec71
Dave Rolsky wrote:
You do realize that mapping time zones to countries will take a _lot_ of
maintenance, right?
Countries are changing all the time. Think back to the end of the cold
war, when the USSR dissolved, along with Yugoslavio and Czechoslovakia,
and at the same time E & W Germany became a
On Wed, 24 Sep 2003 [EMAIL PROTECTED] wrote:
> This is a bit of a beef I have (as of earlier
> today) with the Olson project. I've managed
> to auto-map about 174 of the olson zones to
> geographic places but am scared I may have to
> do the rest by hand. I wish the names were
> more along the lin
Michael Fair <[EMAIL PROTECTED]> wrote:
> For instance, "So what's the time in Ireland?"
> Do you use "Europe/Dublin" or
"Europe/Belfast"? What's the
> difference?
> Do you expect the end user to know that
Dublin and Belfast are in
> Ireland
> before they can see the time in Ireland?
This is a bi
> "Joshua" == Joshua Hoblitt <[EMAIL PROTECTED]> writes:
Joshua> You have incorrectly attributed that comment to me.
No, he had two chevrons in front of the text. This correctly
attributes it as something you quoted.
Although, it'd be nice if everyone used Emacs supercite instead
of chevron
> On Tue, Sep 23, 2003 at 04:55:02PM -1000, Joshua Hoblitt
<[EMAIL PROTECTED]> wrote:
> > > I gaurantee you there are not 364 timezone/DST rules in use in the
> > > world today. The 364 zones are only needed if you are using dates
> > > in the past, which I'm not. Future timezone changes are a di
Josh,
My deepest apologies for misunderstanding the Alias modules both
times I read it over.
You are totally correct in that Alias is very similar to what I'm
looking for and that like what Ben suggested of using submodules
of Alias I can get what I'm after.
> > UI for end user selection would
> Ok - you have to write a small amount of glue code for your application.
Since I'm not trying to present my users with the full list of 364 zone
names
I expect to need to do some filtering and maintenance.
I started out with the idea that "You know, most applications probably
don't need to pres
I agree with Joshua's intent. I think that the timezone selection
right now is the most difficult part of using DateTime if the user has
to specify it (and especially if you are not using a GUI).
I agree that changing DT::TZ is probably not the right thing to do.
Perhaps there should be a DT::TZ:
> It's become painfully obvious that having end users choose
a timezone based on the huge list that is provided natively
by DateTime::TimeZone::all_names just isn't very practical
at this time. (Perhaps in the future when more people are
used to dealing with the Olson names.)
Is there anyw
> It's become painfully obvious that having end users choose
> a timezone based on the huge list that is provided natively
> by DateTime::TimeZone::all_names just isn't very practical
> at this time. (Perhaps in the future when more people are
> used to dealing with the Olson names.)
> Is there
15 matches
Mail list logo
