[OpenAFS-devel] AFS vs UNICODE

[Erik Dalén]

u+openafsdev-t07O@chalmers.se wrote:
> Hello Erik,
> 
> On Wed, May 07, 2008 at 03:04:25AM +0200, Erik Dalén wrote:
>> On Wed, May 7, 2008 at 12:30 AM,  <u+openafsdev-t07O@chalmers.se> wrote:
>>>  Applying encodings to file names (treating them as text as opposite to
>>>  byte sequences) is broken fundamentally - this can _not_ be done properly.
>>>
>> Well, the bug is really in Mac OS X, the issue is if we should have a
>> workaround for it or not. Could file a bug with apple and with luck
>> they'll fix it in 10 years. Or we could normalize the file names in
>> the mac clients.
> 
> It is not a bug, it is wrong design. Windows and MacOS X behave differently
> but this does not mean any of them is "buggy".

It is a bug. When it creates the resource fork for a file called 
mötley.mp3 for example it will use UTF-8 decomposed for the resource 
fork regardless of the normalization of the original file. And then when 
the resource fork and original file have different names it refuses to 
work properly. Even if the standard normalization for Mac OS X is 
decomposed it should work correctly with composed UTF-8 file names. So 
it is definitely a bug in Mac OS X. You can probably replicate this bug 
on Mac OS without using AFS at all.


--
Erik Dalén