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

["James Seng/Personal" <James@Seng.cc>]

> The SC character set has been used for decades and has went
> through extensive nationwide testing in China.  SC is stable and they
are
> properly reflected in Unicode standard.   The question is a
definition:
> is TC/SC a case folding?  It seems that in this WG, there has no
> consensus on this definition yet.

I am not sure what you mean by "properly reflected" in Unicode Standard.
If you mean it is in ISO10646 codepoints, then yes, both TC/SC are in
the code points. But if you saying Unicode Consortium have proper
definition of TC/SC, then I afraid to say there is none.

> One solution is to push the hot sweet potato to zonefile, but as you
have
> pointed out, only Chinese zone will do this.  If I am in US, it may be
> hopeless for me  to see Chinese characters on my domain name
> forever.

Correction: Assuming TC/SC is handled per zone, then it would be up to
the zone admin to decide if he wish to put in TC/SC in the zone or not.
It does not matter where you are, US or China.

> However, the implementation as you have described can be
> implemented in [nameprep] with Unicode as the primary reference
> code, provided the character mapping issue has been settled with
> your option 1.  And we are back to the case folding definition.
> I offer my definition:  case folding is from a key with one look up
> into a data table, and you can obtain another key from the search.

Yes, treating TC/SC like "case-folding" is one of the possible way to do
it altho it introduce other difficulties. However, this wg is not the
right place to discuss codepoint property or any "correction" to Unicode
case-folding/normalization tables/mappings.

The following questions does sound interesting. Would appreciate if you
can post the result to the wg after you gather the responses.

-James Seng

> In any case, I agree with you that this WG needs a list to collect
> each SCRIPT user/engineers' input regarding user's wish list.
>  I've come up with the following questionary for comments.
>
> 1. Your script name (refer to a name defined in Unicode):
>
> 2. How familar are you with the script? How often do you
>   use the script?
>
> 3. What do you expecting your IDN hostname look like?
>
> 4. Does your script is used interchagebly with another script?
>    If yes, then which ones? Are they used as a mixed string?
>
> 5. How does your script  dealing with foreign concept?
>
> 6. How does your script  dealing with foreign sounds?
>
> 7. Do you wish your script could mix with other scripts?
>   If you do, then which script do you think is most useful
>   for your script to accommodating?
>
> 8. As an engineer, what part of the use of your script is
> relatively universal such that there will be no serious
> controversal against it to be fixed by IDN implementation?
>
> 9. As an engineer, what part of the use of your script is
> often controversal, such that IDN shall avoid it in
>  IDN implementation?