Re: [idn] opting out of SC/TC equivalence

[=?utf-8?B?dHNlbmdsbUDoqIjntrLkuK3lv4Mu5Lit5aSnLnR3?= <tsenglm@cc.ncu.edu.tw>]

Hi !  Fältström :
        I had ask you a question in our discussion why not also put alphabet
case holding in keyword system ?
I do not like to push things in this way,  that must hurt everybody, but I
must point out how many cobinations of name in  case mixing of  Alphabet
will be produced in name registration ?
        Even in CJK area , we all have no complete total solution to reduce
the complexity in this open set characteristics, but it not means we do not
care it.  The confusing must be reduced as more as possible, no to produce
them more by keyword system. I think it is unfair to let keyword system
become a trouble sources of CJK characters.

> --On 2001-08-30 08.41 +0200 Harald Tveit Alvestrand <harald@alvestrand.no>
> wrote:
>
> >>  I hope my explaination can shed a little
> >>  light on CNNIC's feeling about TC/SC arguements.  You also
> >> can tell me that my input is out of the scope of this group, and
> >> I am ready to leave too.
> >
> > I think the group will have a better chance of delivering output that is
> > useful to both you and me if we declare that the TC/SC issue is not
going
> > to be solved inside the IDN work.
> >
> > I believe this problem is hard enough that it has to be solved at
another
> > level. Sorry about that.
>
> Just because nameprep and what the IDN group is doing is only mechanical
> operations on individual characters in a single character set, my view is
> that SC<->TC conversion can only be done in a keyword like system before
> IDN is even started to be used.
>
> Reason for this is because of the different kind of equality which James
> described about a year ago and also described in this document. Especially
> see section 2.4.3 about the need for user interaction.
>
> http://www.basistech.com/articles/C2C.html

I must  say that most of them are language related , not related to
easy-to-confuse scipts or characters.
>
> So, outside of IDN, but most certainly part of a system which is described
> in the individual drafts by Dr. Klensin and Mr. Mealling.
>
> Further, as James pointed out, if a registry want to set a policy on what
> subset of the characters which IDN group is allowing is to be allowed
> (only), that is perfectly alright, but also not part of what the IDN group
> is doing.
>

L.M.Tseng