Case preserving has been there, and it is nice for people who wants to support it. To make it a requirement will ensure a uniform support, and ensure a clear path for mixed use of scripts and CJK character recovery cross all types of devices, which adds more software work but benefit a general public on a long run. Given this does not effect DNS structurally, I don't see why we can not make it a requirement.
If you only think in terms of all Latin upper case, it may not make that much a difference. If you think SomethingLikeThis.com it does make a lot of difference, since we don't have that white space already. When we speak about CJK characters, people can tell some Kanji from Han in an equivalent CJK set. Liana On Tue, 09 Oct 2001 06:30:18 +0100 David Hopwood <[EMAIL PROTECTED]> writes: > -----BEGIN PGP SIGNED MESSAGE----- > > [EMAIL PROTECTED] wrote: > > If IDN is going to be universal to all devices, then a > > handheld device may have uppercase support for > > a sick user to have a familar reading quickly. So > > I think your case preserving arguement should be > > considered. > > That doesn't sound like a very strong argument for case preservation > to me. Suppose for the sake of argument that a user does find > uppercase characters easier to read [*]. In that case, all names > should > be displayed as uppercase to that user, not just names that were > originally entered as uppercase. That could be done regardless of > whether the IDN proposal supports case preservation. > > > [*] Personally I find them less readable. Font size and style is > much > more important than case. > > - -- > David Hopwood <[EMAIL PROTECTED]> >
