On Dec 22, 2004, at 5:44 AM, Branko Čibej wrote:
> Then there's the horrible issue of broken tools changing file case on
> you behind your back (this tends to happen too often on Windows),
> usually after some version of the file has alrealy been committed. SVN
> could detect this change locally, but because of the OS/FS/locale
> dependencies I mentioned above, we must find a way to do this
> /without/ using strcasecmp. (Why? Because SVN uses UTF-8 internally,
> and there's no locale-independent case-folding function).
I just thought I would point out that both Windows and Mac OS X use
Unicode for filesystem operations, regardless of the locale. There
must be methods available to deal with the case-folding, since the main
svn-supported OSes that are case-insensitive are already dealing with
that.
Of the 3 primary OSes supported (Linux, Windows, Mac) two of the three
are case-preserving, case-insensitive, one is case-sensitive. It makes
sense to support case-sensitivity as a subset of case-preserving, but
not at the expense of crippling the other two major platforms.
The thread is about renaming on case-preserving case-insensitive
filesystems. Does anyone disagree that such an operation should work
as expected by users of those filesystems? We really didn't need for
the discussion to go on for so long. We all know that there are
incompatibilities between the two systems, those have to be dealt with
regardless... but the rename operation should "just work" if there is
no conflicting file already in the repository.
Scott
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Dec 22 19:14:54 2004