[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:07:06 CET

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

> My first instinct was "the comment is redundant" since it duplicates
> the documented behaviour of the function. Then I realised that the
> documentation doesn't mention UTF-8, so I started thinking about the
> URL. It's already UTF-8 isn't it? Whether the decoded URL is UTF-8

AFAIK yes. The whole subversion library expects paths and
urls in UTF-8 format.

> 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.

URLs/paths returned by the subversion libraries are usually also
encoded that way (UTF-8 and for URL's additionally URI).
I guess the only exception to that is the svn_client_ls() command
which provides the filelist already de-URI encoded.

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
Am I wrong here with my assumptions?


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:08:33 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.