Hi,
Subversion has standardized to store file names encoded as UTF-8 in the repository. But, there are different types of UTF-8 and Subversion has not defined what type to use. Windows and Linux (usually) create files with the so-called composed UTF-8 variant, Mac OS X uses the decomposed UTF-8 variant (the same character will be stored as two characters on the file system). Even if creating a file on Mac OS X using the composed form, it will be stored and reported by the file system in the decomposed form.
Subversion maintains a list of the version controlled files of the current directory in the
.svn administrative directory. When using the
svn status command (used by Syncro SVN Client to list the files in the Working Copy view), it basically compares this list with the file names reported from the file system. Problems occur if this list of version controlled files is using a different UTF-8 variant than the file system reports its files. Until now, Subversion command-line client has no knowledge about the different UTF-8 variants, so it compares the file names incorrectly.
Most quickest solution (but not the best) is to avoid files with umlauts (or any other type of accents) in their names.
You can read more about this issue on:
Best Regards,
Florin Avram
----------------------
Syncro SVN Client Team