Peter N. Lundblad wrote:
> The @peg notation is handle before the path is treated like an URL. If you
Ah, I see.
> need an @ sign in the URL, you can get it by ending the target with an @
> sign.
>
> The problem with escaping characters that have a special meaning in URLs
> automatically is that if someone, for some reason, needs to have an # in
> the URL, they can't get it, because it would be auto-escaped and thereby
> loose its special significance.
I can't see such a reason at the moment, but okay, you are right.
Hmm, give me one more try ;-)
Supposed there is a reason to use a '#' in a URL, the Subversion
client will always end up with the "is not properly
URI-encoded"-message.
IMHO that means that first the client would have to be changed
before a '#' could be used and so it makes sense again to use my
patch (including other characters) - at least until the client
is changed to handle '#'.
Or am I totally confused now?
>
> > So my proposal is to escape as many characters as possible to
> > make the use of the Subversion URLs as convenient for the
> > users as possible and "to replace every occurence of 'URL' in
> > Subversion with 'URL-like path notation' or something like
> > that".
> >
>
> No. I think you have to live with the fact that in URLs, some ASCII range
> characters have to be escaped manually. The same applies for the percent
> character, for example.
>
Anyway, if I have to live with this fact, I will do so (now as
I am aware of it it is half as worse :-) ).
Mathias
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Feb 24 13:54:48 2006