Bug#304541: svn_load_dirs and UTF-8

[Peter Samuelson]

tags 304541 upstream wontfix
thanks

[Yann Dirson]
> Here is an excerpt from a load_dirs session involving UTF8-encoded
> filenames that appear to confuse some of the tools.

Please correct me if I misunderstood your bug report!

It's a consequence of a fundamental design decision in Subversion: it
always assumes that all local filenames are in your current locale.
Filenames are stored as UTF-8 in the repository, and converted back and
forth from your locale when dealing with your local filesystem or
printing to your local terminal.

If your filenames (used in operations like 'svn import' or 'svn add' or
'svn rename') do *not* match your current locale, Subversion will not
do the right thing.  You may or may not agree with the design, but it's
not considered a bug and it's not going to change.

> It may also be useful to add quotes around all filenames lacking them
> (eg. the last error message).

I took a look at svn_load_dirs and did not spot any places where
filenames were left unquoted for the shell.  With Perl programs, it's
not hard to manage filenames safely.  The only iffy spot I saw was in
an section specific to Win32 (working around a lack of fork()).  (It's
also possible that the filename quoting issue was fixed between 1.1.3,
which you reported, and 1.3.0, which I'm looking at.)

Anyway, this seems unrelated to your actual bug report - does it only
happen with your mix of Latin-1 and UTF-8 filenames or do other
filenames confuse svn_load_dirs too?

Peter
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
Url : http://lists.alioth.debian.org/pipermail/pkg-subversion-maintainers/attachments/20060103/a2213176/attachment-0001.pgp