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

[Dmitry Potapov <dpotapov@gmail.com>]

On Mon, Jan 21, 2008 at 11:43:54AM -0500, Kevin Ballard wrote:
> 
> I agree. Every single problem that I can recall Linus bringing up as a  
> consequence of HFS+ treating filenames as strings is in fact only a  
> problem if you then think of the filename as octets at some point.

At *some* point everything stored in computers is a sequence of octets.
In fact, the whole point of the Unicode standard is to define characters
and how to map each character to a unique number (code points) and then
how to encode this number into sequence of octets.

> If  
> you stick with UTF-8 equivalence comparison the entire time, then  
> everything just works.

There are more than one equivalence comparison. The unicode standard
defines at least two, and for some other purpose you may want to use
some others, but for some reason you are trying to present that to
work with text means to follow only one type of equivalence the entire
time...

Dmitry