From: Doug Ewell (dewell@adelphia.net)
Date: Sun Mar 06 2005 - 23:40:55 CST
Erik van der Poel <erik at vanderpoel dot org> wrote:
> So, all I'm saying is that by adopting basically all of Unicode 3.2
> and the whole NFKC process for those characters (followed by some
> prohibitions after those steps), Nameprep ended up allowing such
> inappropriate characters as double-struck C to be fed into the mapping
> process. I believe this was unnecessary. Nameprep could instead have
> chosen to return an error upon encountering double-struck C before
> normalization.
But what harm was done by allowing a hard-to-type and
not-very-confusable character like ℂ into the mapping process?
-Doug Ewell
Fullerton, California
http://users.adelphia.net/~dewell/
This archive was generated by hypermail 2.1.5 : Sun Mar 06 2005 - 23:42:32 CST