From: Mike Eisler (mike@eisler.com)
Date: 01/24/03-12:45:14 PM Z
Message-ID: <3E3189BA.4E535701@eisler.com> Date: Fri, 24 Jan 2003 10:45:14 -0800 From: Mike Eisler <mike@eisler.com> Subject: Re: [Dan.Oscarsson@kiconsulting.se: Comments on NFSv4 rfc3010bis- 05 draft] Mike Eisler wrote: > > Nicolas Williams wrote: > > > Er, no, utf8str_cs requires that a normalization form be used, just not > > on the wire. So the problem of legacy filesystems remains even if we do > > not act to recommend or require a specific normalization form on the > > wire. > > It requires a normalization form only if the server is case insensitive. > > > > At least I feel the need for a "Normalization Forms for Dummies" document. > > > Maybe other working group members do as well. Any pointers to something > > > that will explain this stuff to those who have not already immersed > > > themsleves in this area. > > > > There are several books with "Unicode" in the title (none in my office > > right now). And the Unicode home page is a good place to start: > > > > http://www.unicode.org/ > > I find each visit to unicode.org ever more confusing. My most > recent visit revealed that "16 bit" Unicode now has over 2^64 characters. ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ try: "over 2^16 characters". Point holds though.
This archive was generated by hypermail 2.1.2 : 03/04/05-01:50:48 AM Z CST