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

Re: URI-encoding on 1.7 repository?

From: Daniel Shahaf <d.s_at_daniel.shahaf.name>
Date: Sat, 21 Jan 2012 05:00:09 +0200

Garret Wilson wrote on Fri, Jan 20, 2012 at 18:18:24 -0800:
> On 1/20/2012 6:14 PM, Daniel Shahaf wrote:
> >You don't care what FS backend the server runs. All you care is
> >that the endpoint of svn_ra_open4() implements the Subversion RA
> >API properly. Normal Subversion servers use svn_fs.h which in turn
> >presents the same API _regardless of which backend is used_. I'll
> >spell it out: the notion of 'valid pathname in a Subversion
> >filesystem' does not depend on the FS backend in use.
> All that is good news. So I guess the important question is: what
> spells out "the notion of 'valid pathname on a Subversion
> filesystem'"? Is it "any valid Unicode code point?" What I'm getting

See my previous reply.

> at is that I need to know which characters, if any, I need to encode
> before passing them to Subversion. If Subversion supports any
> Unicode character, I can just pass the path decoded and sleep
> soundly at night. If not, I need to know which ones to decode and
> which ones to pass through.

Err, that depends on what API layer you're working with. (For example:
svn_fs.h is perfectly happy with :,*,\n as part of the basename, but
libsvn_wc on windows, and the mergeinfo logic, aren't.)

And 'what to encode/decode' is a rather vague question. I'm not sure if
it means "Does `svn info uri:///foo bar` == `svn info uri:///foo%20bar`?"
or something else. Can you be more concrete?

> Garret
Received on 2012-01-21 04:01:02 CET

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