[no subject]

[YangWoo Ko <yw@mrko.pe.kr>]

IETF idn working group <idn@ops.ietf.org>
Subject: Re: [idn] Document Status?
Mime-Version: 1.0
Content-Type: text/plain; charset=euc-kr
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <815826.1030921103@localhost>
User-Agent: Mutt/1.3.99i
Sender: owner-idn@ops.ietf.org
Precedence: bulk

Dear IDN working group members,

Within the context of Domain Name, can somebody teach me the benefit of
using "script" instead of "language", or its reverse ? Can somebody
teach me the benefit of using "multilingualization" instead of
"internationalization" ? I am lost.

Regards

On Sun, Sep 01, 2002 at 10:58:23PM -0400, John C Klensin wrote:
> --On Monday, September 02, 2002 10:40 AM +0800 James Seng
> <jseng@pobox.org.sg> wrote:
>
> >...
> > Domain name deal with script. It has no capability to deal
> > with language. When I write a domain name on a napkin (aka
> > "the napkin test"), say "??¨ú???.com", and you give it to
> > someone else, you have no way knowing this is a chinese or
> > japanese or korean without me telling you (out-of-band
> > communication).
>
> Actually, James, domain names don't deal with scripts, either.
> They deal with characters, chosen without restrictions from a
> repertoire.  As long as that repertiore is, as the IDN WG has
> specified so far, all of Unicode less some prohibited characters
> (or, more precisely, code points) than any of the non-prohibited
> Unicode characters can appear in a DNS name, in any order, with
> no restriction to, e.g., script homogenity within a label.
>
> > So in domain name, we cant do "multilingual". We do
> > "internationalization". If you want "multilingual", you are
> > not looking at domain name but something else.
>
> Yes.  But, again, no restrictions to scripts either.
>
>      john
>
>

--
Time to apologize, president Bush
--
/*------------------------------------------------
  Ko, YangWoo / a human / yw@mrko.pe.kr
------------------------------------------------*/