svnx cannot handle filenames with Umlaute (i.e. äöü)

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Add files with umlaute in filename to repository

What is the expected output? What do you see instead?
The files with umlaute are always listed blue with '?' and red with '!P' 
eventhough the local files are identical to the repository. 

What version of the product are you using? On what operating system?
svnx Version 1.3
Mac OS X Version 10.6.6

Please provide any additional information below.

Original issue reported on code.google.com by dkaes...@gmail.com on 18 Mar 2011 at 3:29

[GoogleCodeExporter]

It looks like you’ve been bitten by the infamous NFC vs NFD Subversion bug.
See 
<http://svn.apache.org/repos/asf/subversion/trunk/notes/unicode-composition-for-
filenames>
and <http://subversion.tigris.org/issues/show_bug.cgi?id=2464>.

The Subversion command line tool exhibits the same problem (naturally).
I don’t know if there’s much I can do about it until they fix it in 
Subversion.
There may be patched versions of Subversion floating about the web with fixes 
or workarounds - I don’t know.

Note: If you rename (Move) the file (to the same name) using svnX’s 
Repository window it should ‘fix’ your problem,
but any colleagues on Windows/Linux may not thank you, especially if there are 
multiple files requiring this fix.

Original comment by chris...@gmail.com on 18 Mar 2011 at 5:36

[GoogleCodeExporter]

I don’t intend to look into this any further until they fix it in Subversion.

Original comment by chris...@gmail.com on 14 Apr 2011 at 1:08

• Changed state: WontFix

[GoogleCodeExporter]

Issue 175 has been merged into this issue.

Original comment by chris...@gmail.com on 24 Jun 2012 at 4:46

[GoogleCodeExporter]

First of all, thanks for the fast consideration and review of the issue: this 
is a great project, which gives such fast turnaround. I also understand there 
will not be a workaround in svnX.

I wondered about svn and found that there the issue seems to be open already 
for a very long time, but it seems they are not working on this anymore. 
http://subversion.tigris.org/issues/show_bug.cgi?id=2464
This is a pity. It basically means in cases where multi-platform (including Mac 
OSX) is involved and it is not possible to ensure that no special characters 
are in file names, this may not be used. 

I posted an update at the svn issue tracker. Perhaps they solve it some day.

Original comment by Klaus.Sc...@gmail.com on 24 Jun 2012 at 5:42

[GoogleCodeExporter]

Issue 186 has been merged into this issue.

Original comment by chris...@gmail.com on 22 Oct 2012 at 1:30

[GoogleCodeExporter]

Issue 209 has been merged into this issue.

Original comment by chris...@gmail.com on 21 May 2014 at 12:47