Since SmartSVN has been switched from SVNKit to JavaHL (in version 8.5), we have a quite large amount of users complaining about problems with special characters in file names on Mac OSX.

This is in particular a problem for SmartSVN, because SVNKit was automatically converting to composed form before storing a file in repository and decomposing automatically when writing to the file system. Hence, repositories and working copies which are working fine with version 8, suddenly start breaking with version 8.5.

I understand that an all-embracing solution to issue 2464 is not trivial. On the other hand, there seem to be patches which are working quite well and which could solve mentioned issues when combined with a Subversion config option like "miscellany.autoComposeUTF8", so users have the choice whether *always* storing file names in composed or decomposed form in repository.

Any ideas on this issue are appreciated.

-Marc



Reply via email to