Thread (152 messages) flat view 152 messages, 23 authors, 2016-06-15

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

From: Dmitry Potapov <hidden>
Date: 2016-06-15 22:44:07

On Mon, Jan 21, 2008 at 03:53:10PM -0500, Kevin Ballard wrote:
On Jan 21, 2008, at 3:43 PM, Dmitry Potapov wrote:
quoted
On Mon, Jan 21, 2008 at 11:59:24AM -0500, Kevin Ballard wrote:
quoted
No, it's a question of hashing algorithm. And it's one that's fairly
easily solved simply by picking a specific nonambiguous UTF-8  
encoding
before hashing.
UTF-8 is a *single* encoding, and it maps every Unicode character to
a unique binary representation. So, it is completely nonambiguous.
In this case, encoding refers to normalization form,
I thought we spoke about HFS+, and it does not use any normalization
form, because normalization should produce binary identitical strings
for equivalent strings and HFS+ conversion does not. So, it looks
like you redefine both words "encoding" and "normalization" here.
as other people  
have used it in the conversation besides me.
All your arguments based on confusion and the fact that some other
people were probably confused does not make your arguments any more
valid.
I suggest you stop trying to find inconsequential stuff to argue  
about, especially when a tiny bit of critical thinking would reveal  
the answer.
IMHO, most of your arguments are inconsequential stuff, so I am not
sure what I am supposed to do about your writings. Probably, it does
not make sense to respond your mails anymore...

As to critical thinking, it definitely reveals that Apple's choice
was far from being. Is it so difficult to accept?

Anyway, if you think that you know better than other how to properly
deal with the problem, why don't you try to actually *do* something
and write some code that works as your propose.

Dmitry
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help