Hello,
Yes, in the most of the cases SVNURL#parseURIEncoded should be used. But if you
really want to parse
URL-decoded string, encode it with SVNEncodingUtil#uriEncode explicitly first
(actually SVNURL class
keeps both URL-encoded and URL-decoded URL paths, so don't think about it as
about redundant
encoding/decoding), and then parse with SVNURL#parseURIEncoded.
Deprecation of SVNURL#parseURIDecoded allowed us to catch many bugs in SVNKit
itself, and I believe
it will allow SVNKit users to avoid double encoding bugs, too.
Alternatively you can use SVNEncodingUtil#autoURIEncode: it encodes URLs only
when necessary.
Usually it is used when the URL is entered by user. E.g.
SVNEncodingUtil.autoURIEncode("http://host/path with space") gives
"http://host/path%20with%20space";
But SVNEncodingUtil.autoURIEncode("http://host/path%20with%20space";) also gives
"http://host/path%20with%20space";
--
Dmitry Pavlenko,
TMate Software,
http://subgit.com/ - git-svn bridge
> Hi,
>
> what should I use instead of SVNURL.parseURIDecoded(url)?
>
> Regards,
>
> Zsolt
