Stefan Küng wrote:
> On 15.06.2010 18:58, David Balažic wrote:
> > Stefan Küng wrote:
> >>> 1.) Windows XP Pro SP3
> >>> 2.) Yes, I can also put documents on the web that have the percent
> >>> sign in their path. Don't see your point.
> >> But on the web, those paths need to be escaped.
> >> A file:/// url on Windows doesn't need escaping to work:
> >> file:///c:/program files/myfile
> >> works too, so there's a problem.
> >> On a webserver, a space in an url is not allowed. For windows
> >> file:///
> >> urls it is allowed.
> > I created a folder called C:\Program%20files
> > I can reference both this and the original without any ambiguity.
> > file:///C:/Program%2520files/ -> opens the new one
> > file:///C:/Program%20files/ -> opens the old one
> > Maybe the OS API used by (T)SVN has some bu^Wfeatures
> regarding this.
> > Again, I don't understand why is it a problem, that
> unescaped URLs also work?
> > Just use escaped ones, they work also. (I'm probably
> missing something,
> > as I have not looked into actual (T)SVN code)
> Now try these:
In both cases I get an error dialog saying:
The specified path does not exist. Check the path, and then try again.
Seems as expected?
> You see: the svn file:/// urls always point to (locally) non-existing
> paths since they're inside the repository (which has no corresponding
> path locally).
> Windows can deal with spaces in such an url, so it checks the
> of such local paths to find out which path was meant with the url
> (escaped or not). But that fails terribly if the path doesn't exist.
> So escaped file:/// urls just don't work if the path there doesn't
> really exist.
> TSVN escapes all urls properly, even file:/// ones.
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2010-06-15 19:12:57 CEST