Gaspar Sinai wrote on 2002-02-22 13:25 UTC: > I was thinking about this: maybe the NFS server could enforce > normalization form 'C' so that only the precomposed variant: > > U+00F6 ö > > could create a file. A huge number of scripts could be supported, > without duplicate filenames. Hangul would immediatelly be ok > without the need of jamo decomposition. And we are also very > lucky that CJK can not be decomposed to radicals :) > > I admit this would create some problems...
... starting with violating spirit of the POSIX standard for instance, which contains already a lengthy rationale on why case normalization is not allowed. No. If you are worried about filenames that are not in NFC, then for example you can extend the GNU "find" command with a new predicate that tests whether whether a file name is not in NFC. This way, worried people can very quickly list all files on a harddisk that are not in NFC and then apply little script that does the normalization or some other desired action manually. Problem solved, without any unpleasant surprises. I think I speak for a lot of experienced Unix people if I say that we really do *not* want to have any Unicode normalization code in the kernel. Unix kernels remain mostly character encoding ignorant, and Unicode changes nothing here. Markus -- Markus G. Kuhn, Computer Laboratory, University of Cambridge, UK Email: mkuhn at acm.org, WWW: <http://www.cl.cam.ac.uk/~mgk25/> -- Linux-UTF8: i18n of Linux on all levels Archive: http://mail.nl.linux.org/linux-utf8/
