Re: A character is in the eye of the beholder
> > From w3.org!www-international-request Fri Oct 25 01:58:59 1996
> > Return-Path: <firstname.lastname@example.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
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.