On Sun, 2006-06-04 at 11:18 +0300, Amit Schwartz wrote: > It causes a lot of problems when daylight changes (some code uses Joda > and some is using the Java date Apis). > > For example, EST and MST are calculated differently. > > Are you aware of this problem? > > Is there a solution???
Is it Daylight savings changes? Is it all such changes? Note: MST/EST are not the recommended names for the timezones which the Olsen DB calls America/New_York America/Denver (or whatever they are called). Such Olsen DB style longer names are a better way to refer to a timezone definition. For example EST is NOT a unique 3 letter designation for local time around the world. There is no standard and unique set of such three letter codes, because there is no standards body for these (not that there should be). It is also the case, that EST, MDT, CET etc. only designate "half" of a rule for a local time. In the US, we might call the combination of Pacific Standard Time and Pacific Daylight Time, "Pacific Time", but that is NOT the legal name for it in either Canada or the US, and it certainly wouldn't be useful name for the same GMT/UTC offset for the ajoining region of Mexico (even if we called it "Tiempo Pacifico"), because more than one set of timezone rules borders the Pacific Coast of Mexico. _a_ name of the _current_ set of rules is America/Los Angeles, or America/Vancouver or America/Tijuana ... which all have _historic_ differences. Given the above, I would be interested in some actual example code complete with _long_ formatted times which include the zone designator to see how the different times are different. good luck, -Paul _______________________________________________ Joda-interest mailing list Joda-interest@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/joda-interest
