- From: Mark Davis <mark.davis@jtcsv.com>
- Date: Mon, 28 Jul 2003 18:30:32 -0700
- To: "Carl W. Brown" <cbrown@xnetinc.com>, <www-international@w3.org>
There are a few concepts that are important to make clear, and that are often confused. 1. locale: meaning a locale ID, OR data associated with a locale ID, OR a set of user perferences having something to do with location or language or maybe other stuff. These are quite different. 2. time zones: meaning the zone as defined in the Olson data, OR a format for such a time zone. The latter definitely belong in locales, just a number formats do. The definition of timezones themselves, I believe, do not. Mark __________________________________ http://www.macchiato.com ► “Eppur si muove” ◄ ----- Original Message ----- From: "Carl W. Brown" <cbrown@xnetinc.com> To: <www-international@w3.org> Sent: Monday, July 28, 2003 17:28 Subject: RE: Can servlet know the timezone of the browser? > > Paul, > > I think of a locale as a set of data for parameters that are universal that > vary by either language or location. In this broad definition things like > mailing address formats and time zones fit in the criteria as well as the > traditional locale parameters. I do not believe that they have to be > universal to most applications. You speak of cultural preferences. While > times zones are partially geophysical they are also cultural. Time zones > have disputed boundaries, starting and ending daylight times based on > non-Gregorian calendars, political enclaves who do not want DST, half hour > DST zones. etc. They are often cultural as well. > > My original point is that they can be managed in the application just like > the application manages locales. I feel as such you can consider them an > extention to traditional locales. > > Carl > > > >
Received on Monday, 28 July 2003 21:30:41 UTC