Re: Standardize TimeZone ID

From: Frank Yung-Fong Tang (ytang0648@aol.com)
Date: Mon Apr 26 2004 - 15:27:38 EDT

  • Next message: Michael \(michka\) Kaplan: "Re: Proposal to add 2 Romanian characters"

    The problem is the "Olson ID" itself lack of clear specfication in term
    of RFC kind of format.

    Mark Davis wrote on 4/24/2004, 8:04 PM:

    > LDML does require the Olson IDs to identify time zones (as does Unix,
    > Java,
    > ICU,...). See the discussion in
    > http://www.unicode.org/reports/tr35/.
    >
    > Mark
    > __________________________________
    > http://www.macchiato.com
    > ► शिष्यादिच्छेत्पराजयम् ◄
    >
    > ----- Original Message -----
    > From: "Frank Yung-Fong Tang" <ytang0648@aol.com>
    > To: "Mark Davis" <mark.davis@jtcsv.com>
    > Cc: "Unicode List" <unicode@unicode.org>
    > Sent: Fri, 2004 Apr 23 08:51
    > Subject: OT: Standardize TimeZone ID
    >
    >
    >
    > Is there any standard effort try to standardize Time Zone ID? I am not
    > talking about the Time Zone which refer to a particular time (that could
    > be done by GMT offset or addressed by ISO 8601) itself, but rather
    > talking about an id refer to a particular time zone/ day light saving
    > time rule.
    >
    > I know the de factor standard around is the one in
    > "ftp://elsie.nci.nih.gov/pub/tz" . Probably people also use the timezone
    > value get back from Java a lot.
    >
    > I think a standard (maybe just adopt the one
    > "ftp://elsie.nci.nih.gov/pub/tz" and cleary specify it in RFC) for
    > Timezone ID is important for the future common locale data repository as
    > well as web services i18n.
    >
    > I know this is a little bit off-topic for Unicode, just like the one
    > about locale. Maybe I should move this to w3c i18n mailling list.
    >
    >
    >



    This archive was generated by hypermail 2.1.5 : Mon Apr 26 2004 - 16:03:47 EDT