- From: Keld J|rn Simonsen <keld@dkuug.dk>
- Date: Fri, 25 Oct 1996 19:07:07 +0200
- To: lee@sq.com, mduerst@ifi.unizh.ch, mtbryan@sgml.u-net.com, www-international@w3.org
- Cc: J.Larmouth@iti.salford.ac.uk, rosenne@NetVision.net.il
lee@sq.com writes: > > From w3.org!www-international-request Fri Oct 25 01:58:59 1996 > > Return-Path: <www-international-request@w3.org> > > Received: from gatekeeper.sq.com by sqarc.sq.com with smtp > > So I would rather recommend that we do not mix language > > and the locale, but that we introduce a locale facility in HTTP. > > And abandon the idea of having multiple languages within a single > document? That seems a big price to pay. > > The locale model assumes that you are not in a multilingual environment. > For example, it provides an upper->lower case mapping, but in i18n HTML > you might need so use several different upper/lower mappings in a single > document. I don't see why the locale model cannot handle a multilingual environment. Included in the locale model is that you can shift between locales, or tag data with a locale. Keld
Received on Friday, 25 October 1996 13:09:28 UTC