From: Rick Cameron (Rick.Cameron@crystaldecisions.com)
Date: Sun Apr 27 2003 - 01:40:52 EDT
That would, of course, cause problems - but it doesn't sound to me like the
poser of the question had that in mind. He/she was explicitly using ICU to
do normalisation, and noticed that the O/S is not doing normalisation, and
seemed to be saying that this causes a problem _now_.
From: Chris Jacobs [mailto:firstname.lastname@example.org]
Sent: Friday, 25 April 2003 18:19
To: Rick Cameron; email@example.com
Subject: Re: Unicode Normalization on MS-Windows
----- Original Message -----
From: "Rick Cameron" <Rick.Cameron@crystaldecisions.com>
Sent: Saturday, April 26, 2003 1:29 AM
Subject: RE: Unicode Normalization on MS-Windows
> I don't see the problem, either.
> It sounds like you're saying you would create the file using a
> normalised string for the filename, then later try to open the file
> using an un-normalised string. Why would you do that?
> I would have thought that your program would consistently use a
> normalised string, or an un-normalised one, for both creating and
> opening the file.
Suppose his program consistently used an un-normalised string.
And then suddently the operating system started to normalise everything it
got from his program before using it.
This archive was generated by hypermail 2.1.5 : Sun Apr 27 2003 - 02:31:43 EDT