> > TC/SC tables are just less than 10K, while NFKC/Legacy/Font
> requirements
> > is much higher. implementation complexity is for engineers.
> > but, deployment costs are transferred to innocent end users.
>
> I am not going to argue for or against TC/SC here. I am stuck in the
> middle myself, torn between been a Chinese and been a co-chair for IDN.
>
> But the arguments for inclusive of TC/SC or not should be done on a pure
> technical evaluation basis in IETF. Economy arguments as above is not a
> factor for consideration.
>
> This is why it is known as engineering trade off, not economy trade off.
>
> -James Seng
>
James:
             Let us to know what is pure technical evaluation basis in your
mind as you are a co-chair in an IETF working group.
             If an Engineering Requirement is not related to the user's cost
and what are user need that must be a very interest projects.  I think many
members in IDN WG of IETF also like to know the detail .  You give me a very
strange impression of IETF.  Can someone in IETF can help more ?

L.M.Tseng


  • [idn] Re: [JE... tsenglm@計網中心.中大.tw
    • [idn] Re... James Seng/Personal
      • Re: ... Eric Brunner-Williams in Portland Maine
        • ... James Seng/Personal
          • ... James Seng/Personal
          • ... Eric Brunner-Williams in Portland Maine
            • ... James Seng/Personal
              • ... Eric Brunner-Williams in Portland Maine
                • ... James Seng/Personal
                • ... Eric Brunner-Williams in Portland Maine
                • ... James Seng/Personal

Reply via email to