Re: Proposed resolution: Standardizing on UTF-8 isn't enough

> p.s. IMHO, since Subversion has made the choice to use unicode (UTF-8)
> internally, it should do so *properly*. Perhaps it's overkill to do so
> in connection with this particular defect, but it should be done.

I've seen others refer to "this particular defect" too, but honestly,
there is no other particular defect than that we don't handle Unicode
incorrectly. This just *happens* to show up on Macs more often than
any other OS. Macs aren't broken, our handling of Unicode strings is.

I'm sorry, but I really feel the need to point this out: It just
*happens* to work 99,9999% of the time on Windows... (but it's not
guaranteed to); same thing on *nix.

The net effect is that it's possible to add 2 files with the same name
under a different Unicode representation to Subversion. While it may
be impossible to have case-insensitivity without knowing a locale,
it's surely possible to have NFC/NFD agnostic code without a specific
locale.

bye,

Erik.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Jul 19 13:59:43 2007