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

[Kenneth Whistler <kenw@sybase.com>]

Rick,

> Kenneth,
> 
> from the documentation I have read to date, conversion technology is to be
> provided by existing technology providors or can be developed by the
> registrars. the Registry will not apply the conversion technology, its up
> to the registrar.

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
> > 
> 
>