Re: TR35 (was: Standardize TimeZone ID

From: Mark Davis (mark.davis@jtcsv.com)
Date: Sat May 08 2004 - 12:39:38 CDT

  • Next message: Doug Ewell: ""Country possessions" (was: Re: TR35)"

    It depends on what you mean by "possessions". National Parks? Furniture?
    Occupied countries? ...

    More seriously, this is an messy area. Probably the most fruitful approach would
    have to do is look at the international standards for postal addressing, which
    point off to the individual countries for their own internal subdivisions. You
    would then find out at least what countries *think* they own (or administer --
    I'll refrain from more politically-tinged statements on this list).

    Mark
    __________________________________
    http://www.macchiato.com
    ► शिष्यादिच्छेत्पराजयम् ◄

    ----- Original Message -----
    From: "Carl W. Brown" <cbrown@xnetinc.com>
    To: "Unicode List" <unicode@unicode.org>
    Sent: Sat, 2004 May 08 07:54
    Subject: RE: TR35 (was: Standardize TimeZone ID

    > Mark,
    >
    > Do you know if there is an official list of country possessions?
    >
    > Carl
    >
    > > -----Original Message-----
    > > From: unicode-bounce@unicode.org [mailto:unicode-bounce@unicode.org]On
    > > Behalf Of Mark Davis
    > > Sent: Friday, May 07, 2004 5:28 PM
    > > To: Carl W. Brown; Unicode List
    > > Subject: Re: TR35 (was: Standardize TimeZone ID
    > >
    > >
    > > If you look at LDML, you will see that it uses a narrow view of locale;
    > > essentially those elements that are language-specific +
    > > variations (like choice
    > > of phonebook vs dictionary collation for German). In particular,
    > > a locale does
    > > not include a time zone, nor does it include a currency; those
    > > are considered
    > > orthogonal attributes. What an LDML locale does include is the
    > > capacity to have
    > > *translated names* for time zones, and *translated names* for currencies.
    > >
    > > If someone wants to build a broader notion of locale on top of
    > > this they could
    > > do so, incorporating whatever other information is important for the given
    > > transactional processing, e.g., customer timezone, nearest branch office
    > > timezone, customer's preferred currencies, vendor's allowed
    > > currencies, seat
    > > assignment, dietary restrictions (kosher, atkins, no vegetables
    > > beginning with
    > > the letter C, ...), security status (low-, medium-, high-risk), religious
    > > preference (atheist vs theist), etc.
    > >
    > > Mark
    > > __________________________________
    > > http://www.macchiato.com
    > > ► शिष्यादिच्छेत्पराजयम् ◄
    > >
    > > ----- Original Message -----
    > > From: "Carl W. Brown" <cbrown@xnetinc.com>
    > > To: "Unicode List" <unicode@unicode.org>
    > > Sent: Fri, 2004 May 07 14:46
    > > Subject: RE: TR35 (was: Standardize TimeZone ID
    > >
    > >
    > > > Mark,
    > > >
    > > > > That is not a problem. The Olson IDs are not guaranteed
    > > > > to be unique, just unambiguous. And there are aliases.
    > > > > Typically these are de-unified for political
    > > > > purposes. Thus you may find that two different IDs produce
    > > > > the same results over
    > > > > the entire period of time in the database.
    > > >
    > > > So which timezone will the tr_TR locale in a TR35 database have?
    > > "Asia/Istanbul" or "Europe/Istanbul" or both?
    > > >
    > > > I guess that the territory possessions list should be an
    > > another database that
    > > is merged.
    > > >
    > > > Carl
    > > > >
    > > >
    > > >
    > > >
    > > >
    > > >
    > >
    > >
    > >
    > >
    >
    >
    >
    >
    >



    This archive was generated by hypermail 2.1.5 : Sat May 08 2004 - 12:40:06 CDT