Re: [idn] An ignorant question about TC<-> SC

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

--On 01-10-26 15.13 -0400 ben <ben@cc-www.com> wrote:

> However, what I am certain
> is that you have illustrated the fact that
> applications/clients/users/servers/etc can be made to take advantage
> of this explicit labeling of what "script" an IDN is in and over time
> (with people writing appropriate applications) can be developed into a
> very powerful and useful system.

No, you misunderstood. It is exactly the contrary.

Comparison of characters from two different charsets is extremely
difficult. It can not be done effectively for all combination of charsets.

Only way of dealing with this problem is to map each of the two charsets to
one, and then use comparison rules for that charset.

This is the model which works in DNS, and that is why this wg have chose
this path. This has already been discussed, and discussing this again
doesn't help this wg make progress.

IF you want to start to tag a string (in whatever charset) with meta
information such as language, geographical location of creator of the data,
date and time when the string was created, and use this information when
you do a matching decision, then you talk about something different than
DNS, something which looks like a keyword system. John Klensin has
described such systems in drafts which have circulated on this list.

    paf