- From: Carl W. Brown <cbrown@xnetinc.com>
- Date: Thu, 23 Aug 2001 16:09:36 -0700
- To: "John Cowan" <jcowan@reutershealth.com>
- Cc: "Lenny Turetsky" <LTuretsky@salesforce.com>, "W3intl \(E-mail\)" <www-international@w3.org>
John, You are correct. I just submitted an update for ICU to include all 439 ISO 639 codes. You should use the 2 letter code if there is one. RFC 3066 also provides for the IANA language names like i-klingon and x-anything as well. You can represent all ISO 3166 country codes with two letter codes. IANA character sets can be up to 40 bytes. The largest time zone name is currently 27 characters but I allow for 32 just in case. Variants are typically up to 8 bytes but I have seen 11 byte variants. It is also possible to have compound variants like: es_ES.iso-8859-15@TRADITIONAL-EURO#Europe/Madrid Carl > -----Original Message----- > From: John Cowan [mailto:jcowan@reutershealth.com] > Sent: Thursday, August 23, 2001 2:22 PM > To: Carl W. Brown > Cc: Lenny Turetsky; W3intl (E-mail) > Subject: Re: canonical names for timezones > > > Carl W. Brown wrote: > > > What I last implemented was: > > > > POSIX Format > > > > ll [ _CC ] [ .MM ] [ @VV] > > > > ll = lang, CC = ctry, MM = charmap, VV = variant > > It's also better not to assume that the language code is only > 2 letters. See RFC 3066 for the current state of things: > this allows language codes of indefinite length, containing > letters, digits, and hyphens. > > -- > Not to perambulate || John Cowan <jcowan@reutershealth.com> > the corridors || http://www.reutershealth.com > during the hours of repose || http://www.ccil.org/~cowan > in the boots of ascension. \\ Sign in Austrian ski-resort hotel >
Received on Thursday, 23 August 2001 19:09:33 UTC