From: Dmitry Potapov <dpotapov@gmail.com>
Date: Wed, 23 Jan 2008 17:39:06 GMT
Subject: Re: git on MacOSX and files with decomposed utf-8 file names
Message-ID: <37fcd2780801230939q6d30488bwc78eaeb9eb01989f@mail.gmail.com>
In-Reply-To: <769D0E1A-8399-458B-8328-FF3642D833BC@sb.org>

On Jan 23, 2008 7:58 PM, Kevin Ballard <kevin@sb.org> wrote:
> On Jan 23, 2008, at 4:40 AM, Mike Hommey wrote:
> >
> > That's the point. It's stored in NFC, but what applications see is
> > NFD.
>
> I was actually asking for you to show this instead of just asserting
> it, but I realized I have access to an SMB share myself so I just
> tested.
>
> And you're right. That's very curious. I guess they did that because
> the entire Carbon stack was written assuming NFD (back at the same
> time HFS+ was created), and they wanted to provide a consistent
> interface to applications.

Wait, did you tell us some time ago that normalization does not
matter and you just need to treat strings "as text"? Now, it looks
like the Carbon stack does not treat strings "as text". How come?

Maybe, you should stop lying and admit that changing Unicode
strings does matter even if they remain equivalent.

> Since the filesystem already uses NFC,
> renormalizing to NFD shouldn't lose anything (want the original
> representation back? just normalize back to NFC).

On Windows, you can create two *different* files -- one with NFC
and the other with NFD name. I wonder, how it is going to work
with your renormalization back and force.

Dmitry