On Jan 23, 2008, at 12:39 PM, Dmitry Potapov wrote:
On Jan 23, 2008 7:58 PM, Kevin Ballard <kevin@xxxxxx> wrote:On Jan 23, 2008, at 4:40 AM, Mike Hommey wrote:That's the point. It's stored in NFC, but what applications see is NFD.I was actually asking for you to show this instead of just asserting it, but I realized I have access to an SMB share myself so I just tested. And you're right. That's very curious. I guess they did that because the entire Carbon stack was written assuming NFD (back at the same time HFS+ was created), and they wanted to provide a consistent interface to applications.Wait, did you tell us some time ago that normalization does not matter and you just need to treat strings "as text"? Now, it looks like the Carbon stack does not treat strings "as text". How come?
I'm amazed at how badly you manage to misinterpret everything I say.
Since the filesystem already uses NFC, renormalizing to NFD shouldn't lose anything (want the original representation back? just normalize back to NFC).On Windows, you can create two *different* files -- one with NFC and the other with NFD name. I wonder, how it is going to work with your renormalization back and force.
I'm not sure what you're trying to say here. As near as I can tell, SMB already does encoding conversions itself when talking to different clients, so you can hardly say OS X is doing something bad by converting between local NFD and NFC on SMB.
-Kevin Ballard -- Kevin Ballard http://kevin.sb.org kevin@xxxxxx http://www.tildesoft.com
<<attachment: smime.p7s>>
