Re: [idn] Prohibit CDN code points

[Patrik Fältström <paf@cisco.com>]

--On 2002-01-23 21.47 +0900 YangWoo Ko <newcat@spsoft.co.kr> wrote:

> Your last statement does not exactly describe TC/SC issue. Following may
> explain TC/SC issue better;
> 
> "If one enter a string in Unicode, one may or may not know whether TC or
> SC was used. It depends both on his language in mind when entering that 
> string and on his knowledge about characters."

Correct.

> Dear all members,
> 
> What about having additional prefix(es) for extension like TC/SC issue ? 
> For example, az-- for normal IDNA and bz-- for chinese-extension IDNA 
> and so forth. It may serve as an context information or language tag.

How do you match between one string which uses az--<foo>.com and
bz--<foo>.com where "<foo>" stands for the term "foo" but encoded?

And, yes, you can do this, but as i have pointed out before, this means
every server needs to know about all matching algorithms.

I.e. if you open the box of "problems" with Unicode, you will find that the
SC/TC problem is only one of them. Only one. I guess we have some 20-30
other problems which are similar to the SC/TC, i.e. problems because of
unification or non-unification in Unicode.

So, you will see an explosion of matching rules.

Reason we see this about SC/TC is that that happen to be the problem space
we discuss at the moment. We could aswell discuss the problems with
adiaeresis in the countries and languages which uses it.

My conclusion is the same, every server need to have knowledge about how to
handle all encodings.

   paf