Re: svn blame and filenames with non-ascii chars

Hi Stefan,

> > depends on what characters are URI encoded in the URL, where do we
> > guarantee that the URL contains URI encoded UTF-8?
>
> 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. I think Subversion libraries
assume they always operate on UTF-8 encoded strings. This means that you should
first encode your URL to UTF-8 and then URI-encode it. Reversing the operation
will give a UTF-8 encoded URL.

[ snip ]

> That worked in the past with all functions I use in TSVN - at least
> I haven't found something that doesn't until now (except the blame
> command).
> Am I wrong here with my assumptions?

Maybe in the order of encoding?

bye,

Erik.

-- 
+++ GMX - die erste Adresse für Mail, Message, More +++
Neu: Preissenkung für MMS und FreeMMS! http://www.gmx.net
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org