[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 19:34:15 CET

----- Original Message -----
From: "Erik Huelsmann" <e.huelsmann@gmx.net>
> > 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.

If you have to first do the UTF8 conversion and _then_ do the URI encoding,
then the command line client wouldn't work with most commands. The
command line client expects that the user enters URL's already URI encoded
and then does the UTF8 encoding.
(or does the shell already UTF8 encoding and the client just reads user
input as UTF8? That would really surprise me)

Stefan

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Dec 13 19:35:26 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.