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

Re: svn blame and filenames with non-ascii chars

From: SteveKing <steveking_at_gmx.ch>
Date: 2003-12-13 20:00:50 CET

----- Original Message -----
From: "Philip Martin" <philip@codematters.co.uk>

> >> What I do in TSVN is for paths to encode them in UTF-8 before
> >> passing to the subversion functions, and URL's first URI encoded
> >> and then in UTF-8 before passing to the subversion functions.
> >
> > Are you sure this the correct order? it means that if you decode the
> > URL you can be stuck with a non-UTF-8 encoded URL.
> Exactly. I don't think the command line client gets it right either.

So that's where the whole problem is? In that case I suggest
that (to make it easier for all the clients out there and the
several language bindings) the subversion library should do
the URI encoding and only leave the UTF8 encoding to
the clients. After all, the subversion libs know best if
a path is local/svn/http/... and can do the URI encoding
where necessary.


(ok, I admit, it would also be easier for me :-) )

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Dec 13 20:02:18 2003

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

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