Re: git on MacOSX and files with decomposed utf-8 file names

> On Jan 17, 2008, at 11:10 AM, Johannes Schindelin wrote:
>> [Jay, don't cull Cc: lists on vger.kernel.org.  I consider it rude.]
>>
>> On Thu, 17 Jan 2008, Wincent Colaiuta wrote:
>>
>>> El 17/1/2008, a las 6:15, Junio C Hamano escribió:
>>>
>>>> "Jay Soffian" <jaysoffian+git@gmail.com> writes:
>>>>
>>>>> So here's what I can see as being useful additions to git:
>>>>> ...
>>>>> Thoughts (besides "patches welcomed")?
>>>>
>>>> I think we already discussed a plan to store normalization  
>>>> mapping in
>>>> the index extension section and use it to avoid getting confused by
>>>> readdir(3) that lies to us.  Is there any more thing that need to  
>>>> be
>>>> discussed?
>>
>> Yes, and I think that a lot of time would have more wisely spent on
>> reading that, and trying to implement it, than writing a number of  
>> long
>> mails, repeating the _same_ (refuted) points over and over again.
>
> I searched the archives for the posts about normalization and I  
> could not find them, sorry.
>
> Is stringprep (RFC 3454) being proposed as an optional normalization  
> step before lookups in the index?

> The terms used in this Q&A, decomposed and precomposed, roughly  
> correspond to Unicode Normal Forms D and C, respectively. However,  
> most volume formats do not follow the exact specification for these  
> normal forms. For example, HFS Plus uses a variant of Normal Form D  
> in which U+2000 through U+2FFF, U+F900 through U+FAFF, and U+2F800  
> through U+2FAFF are not decomposed (this avoids problems with round  
> trip conversions from old Mac text encodings). It's likely that your  
> volume format has similar oddities.