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

[David Hopwood <david.hopwood@zetnet.co.uk>]

-----BEGIN PGP SIGNED MESSAGE-----

tsenglm@cc.ncu.edu.tw wrote:
> Patrick Fältström wrote:
> > Further, you say that the number of permutations will be high. [Linguists]
> > I have talked with say that the number of permutations will be low, i.e.
> > that one label is in most cases either in SC or TC.
>
>         That is true in GB and BIG5 , so UNAME draft show the example of
> registration in full SC (pure GB not  GBK) and full TC  not the mixing ,
> but the GBK used in Hong-Kong including part of  frequently used TC
> characters are  mixing  of  SC and TC .  The  chinese.com  does not limit
> the mixing of  SC/TC in UNICODE form.

Provided that input mechanisms can be set to produce all SC or all TC,
does that matter? In practice, would a Chinese input mechanism, as it
would be set up for a user in Hong Kong, say, typically produce an
arbitrary mix of SC and TC characters?

Note that there are other scripts which have special requirements for typing
domain names, URIs and email addresses - for example Arabic and Hebrew. So
in general, fully satisfactory user input of these identifiers will depend
on support from input mechanisms (and in some cases the user telling the
input mechanism that an identifier is being entered, if it appears in free
text). Chinese is just another case where this support would be useful.

- -- 
David Hopwood <david.hopwood@zetnet.co.uk>

Home page & PGP public key: http://www.users.zetnet.co.uk/hopwood/
RSA 2048-bit; fingerprint 71 8E A6 23 0E D3 4C E5  0F 69 8C D4 FA 66 15 01
Nothing in this message is intended to be legally binding. If I revoke a
public key but refuse to specify why, it is because the private key has been
seized under the Regulation of Investigatory Powers Act; see www.fipr.org/rip


-----BEGIN PGP SIGNATURE-----
Version: 2.6.3i
Charset: noconv

iQEVAwUBO45fFzkCAxeYt5gVAQHyGwgAvGsc6tKwq5+eNoxAEfZPYkgO56Oz9yMT
tMK7Ggl+YtIxeJ53IWUcUKR0H0SUwXkqHxVsFo/unQXcU2iq/VMt57oG8HYBE/nh
oMrl4A3hpU4krjJQMnU8HTrkxJ4/N8NQ/85cPH3vXkH4GW4uV6SyWpiFzuwZDJdf
EUhE30t3X/3+8YHF2BU3RdQeH/zvljCsRcNrMLRIAQ6wUcwSyF07tKeH0uHu1QBt
p4pkGPIeztpvKNfqjCMwWzyvaG6N/zs+HSOwUE6dNZsz9jF0WCbJ0pLbDcMdMzv+
3IIpgYcoAiGyKWjWq8nkNZ5E4rn8/+oQ8zdMdKCUPdGBm5B5unLPNA==
=MU4x
-----END PGP SIGNATURE-----