title: How do I configure Subversion to work with URL-encoded characters?
body: <p>I'm trying to check out a Subversion project that I've set up on a remote server. It works fine for most directories, however once it come time to check out a file called "The%20Loft.pdf", the whole process breaks. It looks like it's not able to create the "/.svn/tmp/text-base/" file for it. My guess is that it's having trouble with the %20 character.</p>
  
  <p>The errors is actually:
  svn: Can't open file 'src-holdings/httpdocs/wp-content/blogs.dir/2/files/2010/05/.svn/tmp/text-base/Amanda-Kuda.jpg.svn-base': No such file or directory</p>
  
  <p>Where "Amanda-Kuda.jpg" is the file that follows "The%20Loft.pdf". After looking inside of 
  "/.svn/tmp/text-base/", it looks like all the .svn-base files are getting created except those that follow "The%20Loft.pdf" in checkout order.</p>
  
  <p>How can I reconfigure my server (Linux) or Subversion to handle this type of file without breaking? I would just enforce a "no-spaces" policy, but it's a client's WordPress installation, and I can't count on them to avoid files with spaces.</p>