Hi, On Mon, Jul 14, 2008 at 9:42 AM, P.Hill & E. Goodall <[EMAIL PROTECTED]> wrote: > There is nothing "proper" about converting MET to Middle European Time > or to MiddleEast Time (even though the second one is less common than > the first).
By "proper" I meant in sync with Olson TZ database. And in Olson, MET is officially recognized and it means Middle European Time. Java, as well as Linux, and pretty much everybody else, are now fully use/support Olson database, and joda-time behaves incompatibly there, converting MET to MiddleEast time. > The general problem is that the three letter abbreviations > are not unique (and need not be), so adding additional special case > fallback rules is a difficult to support solution. Indeed. But it is already there, an additional special case for MET in joda-time that converts it to MiddleEast Time. Also, I might imagine that different projects have different priorities. For some, they really want the old compatibility with ancient JDK versions (where MET means MidleEast Time). Others might really want to be compatible to Olson as much as possible. Hence was the suggestion to allow (essentially, to open to joda time clients) the ability to customize those "custom" conversion rules. Currently, they are hardcoded in joda time and very hard to adjust/change. Thanks, --Vladimir ------------------------------------------------------------------------- Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! Studies have shown that voting for your favorite open source project, along with a healthy diet, reduces your potential for chronic lameness and boredom. Vote Now at http://www.sourceforge.net/community/cca08 _______________________________________________ Joda-interest mailing list Joda-interest@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/joda-interest
