On Fri, 24 Feb 2006, Mathias Weinert wrote:
> Peter N. Lundblad wrote:
>
> > 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?
>
Yes, we can change the client to allow that character should we need to,
but if we start autoescaping #, we can't stop doing so until 2.0 for
compatibility reasons.
> > 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 :-) ).
>
Great! :-)
Thanks for the discussion,
//Peter
---------------------------------------------------------------------
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:59:56 2006