Re: utf-8 filenames in phar files.

Yasuo Ohgaki wrote:

BTW, without NFC normalization, I sure there will be unhappy users if users use it with OSX and Linux/Windows. OSX decomposes Unicode and there will be the same name path with different unicode string that appears the same on their terminal/etc on Linux/Windows.

I don't think this problem is any different to the simple conflict between upper and lower case 'normalizing' that happens currently? Each OS has it's own standards and quirks which we have to put up with. It is a simple fact that UTF-8 does NOT have a preferred standard, and everything that is valid has to be handled. This is back to the question on case insensitive comparisons, and if even that can be supported going forward. If different OS's 'normalise' a string for their own purposes can we be expected to provide different comparison rules for each? Or is it something that has to be passed back up the chain for a library to handle more generically? Phar should not 'translate' anything ... it is where these strings are used that should handle any additional processing? -- Lester Caine - G8HFL ----------------------------- Contact - http://lsces.co.uk/wiki/?page=contact L.S.Caine Electronic Services - http://lsces.co.uk EnquirySolve - http://enquirysolve.com/ Model Engineers Digital Workshop - http://medw.co.uk Rainbow Digital Media - http://rainbowdigitalmedia.co.uk