W3C home > Mailing lists > Public > www-international@w3.org > October to December 2001

Re: locales

From: <David_Possin@i2.com>
Date: Wed, 7 Nov 2001 14:13:20 -0600
To: "Tex Texin" <texin@progress.com>
Cc: cbrown@xnetinc.com, www-international@w3.org, www-international-request@w3.org
Message-ID: <OFCE7B1016.32F69AA7-ON86256AFD.006E28FF@i2.com>
Tex,

OK, I will open a locale forum in yahoo.groups, but I need at least 2 
others willing to be managers to ensure quality out of experience, and we 
also do not have time always to be active in the discussions. Looking at 
the discussion so far I see at least 4 potential victims .... ;o) Please 
let me know if there is enough interest to participate, either in the list 
or by direct email. I will archive the threads so far in the message area 
there. It would be nice if we could actually achieve something.

David 





"Tex Texin" <texin@progress.com>
11/07/01 01:53 PM

 
        To:     David_Possin@i2.com
        cc:     cbrown@xnetinc.com, www-international@w3.org, 
www-international-request@w3.org
        Subject:        locales


David,

If you would set up an archived forum, that would be great. It will save
me trying to identify which messages are relevant and saving them all on
my drive.

Mentioning time zones will, I am sure, insure a blast from Carl. (;-) I
look forward to it.)
One point is that a locale may include more than one zone (e.g. US goes
from EST, CST PST) so is ambiguous, and we may go down the trail of the
changes to daylight savings time may vary within a locale.

A key question for me is which of the many variables for
internationalization belong in a locale and which belong in some other
structure?

Maybe time and calendar should not be a function of locale...
Maybe currency should not be.

Which variables are best associated with the locale, which with the
data, and which with the application?
For example, since I develop database products, and I cannot have
indexes changing on me, I always include the rules for sorting in the
database, with the data.

I don't generally worry about hyphenation, I would probably keep rules
for that with the application (the choice being influenced but not
defined by locale).

tex


** === big chop === **

-- 
-------------------------------------------------------------
Tex Texin                    Director, International Business
mailto:Texin@Progress.com    Tel: +1-781-280-4271
the Progress Company         Fax: +1-781-280-4655
-------------------------------------------------------------
"When choosing between two evils, I always like to try the
one I've never tried before."- -Mae West
Received on Wednesday, 7 November 2001 15:19:02 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 2 June 2009 19:16:58 GMT