Re: [idn] NSI Multilingual Testbed Information (fwd)

[James Seng <James@Seng.cc>]

NSI Registry approached is that for each domain names in any languages,
you have to submit different encoding you wish to support. In other
words, if you registered YAHOO.com in (where YAHOO is in Chinese) in
GBK, you have to submit another application that you like this to be in
BIG5.

By default UTF-8 & RACE are also automatically comes with one native
encoding.

So no, NSI Registry does knows encoding != language. They are not
clueless as most people likes to think NSI Registrar is.

Additional application of encoding per domain name does not neccessary
means it is additional registration, neither does it implies there is
addition cost. I believe that details have not work into the RRP yet.

I am wearing multiples hats here so pardon me if I have to be careful
what I am allowed to say and what is not (yet), e.g. Clarification of
public knowledge.
 
-James Seng

Kenneth Whistler wrote:
> Conversion technology refers to *character sets*, not to *languages*.
> 
> >
> > It appears that there is an encoding type for each language, wow looks
> > like NSI figured everingthing out.
> 
> If NSI thinks "there is an encoding type for each language", then they
> haven't figured out squat. Language identity and character encoding
> identity vary more or less independently and orthogonally.
> 
> So which is it:
> 
> A. "for each language in which it will be registering names"
> 
> or
> 
> B. "for each character encoding in which it will be registering names"
> 
> ?
> 
> --Ken Whistler
> 
> >
> > I guess we can all go home now.
> >
> > -rick
> >
> >
> > On Thu, 24 Aug 2000, Kenneth Whistler wrote:
> >
> > > > Multilingual Certification Evaluation
> > > >
> > > > Each registrar must successfully complete a multilingual certification
> > > > evaluation for each language encoding in which it will be registering names.
> > >
> > > Ack!
> > >
> > > What does "language encoding" mean here? This is unfortunately very
> > > imprecise and misleading wording.
> > >
> > > I presume the intent here is for each *character* encoding in which it
> > > will be registering names. Any character encoding could support multiple
> > > different languages (since even ASCII alone can support a number of languages) --
> > > and I don't imagine the multilingual certification evaluation wants to
> > > end up heading down the rathole of trying to determine whether
> > > "beethoven.com" is to be an English certification or a German certification,
> > > for example.
> > >
> > > --Ken Whistler
> > >
> >
> >