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

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

From: Stefan Küng <tortoisesvn_at_gmail.com>
Date: Mon, 13 Jul 2009 20:14:51 +0200

Synetech wrote:
> Stefan Küng wrote:
>> 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 :)
>
>
> Hmm, then I guess the problem is in the checkout/update functions.
>
> If I issue a checkout using the SVN command-line (svn.exe), it can
> properly pull the files from an external that has non-alphanumeric
> characters in the URL. It is the same with AnkhSVN.
>
> Just to make things even more confusing; VisualSVN (which uses
> TortoiseSVN for its main functions) can also correctly pull files from
> an external that contains non-alpha characters in the URL.

That doesn't make any sense. VisualSVN starts TSVN for
checkouts/updates/... so if VisualSVN, then TSVN works (it *is* TSVN
that's doing the job).

Stefan

-- 
        ___
   oo  // \\      "De Chelonian Mobile"
  (_,\/ \_/ \     TortoiseSVN
    \ \_/_\_/>    The coolest Interface to (Sub)Version Control
    /_/   \_\     http://tortoisesvn.net
------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=2371051
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2009-07-13 20:15:17 CEST

This is an archived mail posted to the TortoiseSVN Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.