Re: [idn] Summary of TS-SC discussion

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

> >             I  have  question .   Does  the ACE translation ( ACE-Z or
RACE
> >..) can be done without  any UNICODE table ?
>
> Correct: they do not require tables.
>
         A user type-in a Mutilingual Name (For ex. JIS  code) ,  From  here
to ACE code,
there are a translation table from JIS to UNICODE ,  then based UNICODE data
resultas, you have ACE code .
         To do nameprep , character mapping and forbidden table can not
aviod, If there are no nameprep , there will be no succeed ACE conversion.
the pre-condition is there need table to make sure the input data is in
correct data range.
> >            Does all table in proposed nasmeprep are all widely-accepted
> >official standard table ?
>
> Yes.
      I think many people like to know all the official name and source of
starndard.
> >  > 3) The same code points that would be converted in some domain name
> >>  parts would not be converted in other domain name parts because the
> >>  conversion is only appropriate for Chinese, not Korean or Japanese,
> >>  which use the same code points. Thus, the language (not the script)
> >>  must be known in order to do the conversion correctly.
> >>
> >           You have get the results from any Korean , Japan official
> >announcement ?
>
> Sorry, but I cannot understand the question.
My question is TC/SC conversion is only applied to Chinese character, no
Japanese or Korean can be applied ?
>
> >   The language term is not treated in this WG , why you
> >annouce "all" scripts are "all language dependent" ?
>
> I never said any such thing. Scripts are independent of language, but
> scipt usage can be language-dependent.
>
> >   If it is so, then all
> >scripts of UNICODE should not be treated in IDN.
>
> It is not so.
          So, there are some small part is  scripts only and independent of
language using , like the whole case Latin characters in Japan, Chinese, and
Korean language, they should be treated like the ASCII character case
mapping (For ex.  .COM).
> >          Why the tag in MIME mail header and subject can be recognize
the
> >language character typed-in and display them correctly ?
>
> MIME body part headers allow MIME language tagging; mail subject
> lines do not allow MIME language tagging, but do allow Unicode 3.1
> language tagging. Neither has had much success in implementation, and
> inconsistent use causes poor display.
>
> >   Does user of
> >E-mail tag each part of CJK characters ?
>
> No, they don't. MIME body part headers cover the entire message, not
> individual characters. Unicode 3.1 language tagging is applied to
> groups of characters, but so far, there have been no common
> implementations. This is probably because it is tedious for a user to
> have to insert tags into simple text saying "these characters are
> from this language, but these other characters are from this other
> language".
>
Actually , E-Mail system use language tag , right ?
> >           Another question , why the IDN  domain name must be  IDN.COM ,
why
> >not it is ACE(ML-name.ML-company) ?
>
> Because that is not how the DNS works. What you propose makes perfect
> sense for a directory system, and is being actively pursued in many
> places. In fact, this one of the reasons that people want to abandon
> using the DNS for naming things like companies: it does a very poor
> job of it. The IDN WG work will make that poor job a little better
> (by allowing more characters), but it will still be fairly poor.
>
> >          I  like to know  "Taiwan University"   臺灣大學
> >                                   "Tsinghua University"  清華大學
> >can be solved by  2 records  in DNS zone table with TC/SC mixing ?
>
> One record would be all-traditional, one would be all-simplified.
    Sorry,  it is not true , " Taiwan " means 2 chinese characters, in these
two character , the first one has 2 scripts , all are TC , but one of them
are only used in PRC-SC. The all-traditional need at least 2 record in
"Taiwan University" , this is a example of  1(SC) --> 2 (TC).  1-n mapping
are forced to selected one in registraion is based on the assumption the 1-1
mapping had treated in nameprep. You can not cut them to simplify it and
forget they may be 2^^n combinations  without SC/TC 1-1 mapping to reduce
them.

L.M.Tseng