[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Issue with UTF-8 filenames

From: Etienne Miret <etienne.miret_at_ens-lyon.fr>
Date: Wed, 19 Mar 2008 17:40:48 +0100


I’ve made an import on a svn repository with my locale incorrectly set
to 'fr_FR', which led it to interpret my filenames as ISO-Latin-1,
although they were UTF-8. Hence, the names are currently stored in my
repository in double UTF-8.

After (correctly) setting the locale to 'fr_FR.UTF-8', I ran 'svn
status' on my working directory, and got exactly the result I expected:
   $ svn status
   ? Impérialisme
   ! Impérialisme
The files with the wrong name is reported missing, and the one with the
correct name is reported not to be versioned.

Now I intended to delete my file, and correct the name by a 'svn update'
followed by a 'svn move'. However :
   $ svn update
   A Impérialisme

   $ svn status
   ? Impérialisme
   ? Impérialisme
   ! Impérialisme

   $ rm Impérialisme

   $ svn mv Impérialisme Impérialisme
   A Impérialisme
   svn: Working copy 'Impérialisme' locked
   svn: run 'svn cleanup' to remove locks (type 'svn help cleanup' for

   $ svn status
   ? Impérialisme
   ? Impérialisme
   ! + Impérialisme
   ! Impérialisme
Obviously 'svn' doesn’t correctly compares UTF-8 strings. The issue
seems to be that there are several codes for the same character. For
example 'é' can be 0xC3A9 (LATIN SMALL LETTER E WITH ACUTE) or 0x65CC81
lucky enough for subversion and my OS to always use the same form.

I’m running subversion 1.4.4 on Mac OS X 10.5.2.

Is this a known bug, and is there any workaround?


Etienne Miret
Ne m'envoyez pas de fichier Word SVP, je ne peux pas les lire !
Don't send me Word attachments please, I can't read them!
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-03-19 17:50:24 CET

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.