Ben Collins-Sussman wrote:
> On Sat, 2004-01-17 at 05:31, Florian Weimer wrote:
> > This script tries to create a repository which contains a file name with
> > a non-ASCII character:
> [...]
> > The nasty part is that none of these errors is detected at import time
>
> Why should there a problem at import time? The repository stores all
> paths as UTF8. If your locale can't deal with the UTF8->native
> conversion on checkout, then the client environment is broken, not
> subversion. Or maybe I'm misunderstanding you.
If the locale is set to UTF-8, it is possible to import file names such
as "gr\374n" (consisting of four bytes), and a four-byte file name is
stored in the repository (which is _not_ valid UTF-8).
> > You might end up with a
> > repository which is not fully functional, and you don't know it. 8-(
> >
>
> Set your locale correctly, and everything works fine. Why are you
> committing non-ascii filenames in the first place if your locale doesn't
> understand them? It's not a likely scenario... I don't see how someone
> could be "surprised" by this.
The "svn copy" failure occurs when the locale is set correctly (and the
repository contains a file name properly encoded in UTF-8).
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sat Jan 17 16:35:17 2004