Re: ! Some Characters in Path Cause Troubles (eg in Externals)

Okay, it makes sense.

I just checked several RFC’s (including 3490, 3986, and 3987) and it
seems that the bracketing characters, while not reserved, are on the
not-recommended list for URLs because “gateways and other transport
agents are known to sometimes modify such characters”. So I guess that
only the parentheses are officially allowed un-escaped.

I suppose things won’t get better (eg IRI, IDN, etc. spreading) until
Americans can easily type foreign characters. :|

Well I guess I better get back to my repository. I’m going to re-
import the whole thing again, and set the externals correctly.

--
Synetech
Stefan Küng
> As I said: you have to escape the URL properly (with the %XX sequence).
> Only the target path must be escaped with the backslash.
>
> And neither svn, VisualSVN or AnkhSVN could handle unescaped external
> urls - that how the svn library works which they all use.
…
> The external path is never sent - that's uses locally only (only the
> local client has to know the name of the folder where the externals
> should be stored).
> And TSVN properly escapes all urls in all places, except in the the
> external properties because it would have to parse those properties for
> the urls to escape. And escaping the target path is not an option since
> I'm not aware of a documentation in the svn lib which chars need such
> escaping - so 'guessing' which ones that might be is never a good idea :)
On Jul 13, 2:13 pm, Stefan Küng <tortoise..._at_gmail.com> wrote:
> Synetech wrote:
> > On Jul 13, 8:28 am, Stefan Küng <tortoise..._at_gmail.com> wrote:
> >> you have to enter a properly escaped url, and it's also necessary to
> >> escape the target folder if it contains special chars. But to escape the
> >> target folder, you have to use the '\' char, e.g., "\{Components\}".
>
> > I tried using escaped characters (eg ‘/svn/\{Components\}/Foobar’),
> > and the TSVN checkout didn’t work; I still get an External Failed
> > error. If I URL-encoded the URL in the external (eg ’/svn/%2bComponents
> > %2d/Foobar)’, then TSVN can correctly checkout/update the external
> > files. It’s pretty ugly. It really should be able to work with ‘/svn/
> > {Components}/Foobar’ :(
>
> > (I didn’t check to see if svn, VisualSVN, or AnkhSVN can handle the
> > URL-encoded or escaped external URL since they can all handle a plain
> > one.)
------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=2371095
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].