RE: Problem with file name encoding during merge - URL Encoding (Percent Encoding)

Dear Johan,
at my first e-mail I wrote EXACTLY what to do to reproduce error.
In my opinion this is low chance to blame client library.
We tried two different compilation of 'pure svn' on Windows, and as third: TortoiseSVN client.
Moreover we also tried to reproduce this on Linux machine.

I suppose that this may be connected with http transport, or apache/WebDAV or svn server, because when I create repo on locally and use file:/// transport, then everything is ok.

Bartosz

-----Original Message-----
From: Johan Corveleyn [mailto:jcorvel_at_gmail.com]
Sent: Friday, October 6, 2017 1:30 PM
To: Bartosz Pierzchlewicz
Cc: users_at_subversion.apache.org
Subject: Re: Problem with file name encoding during merge - URL Encoding (Percent Encoding)

On Fri, Oct 6, 2017 at 8:45 AM, Bartosz Pierzchlewicz <Bartosz.Pierzchlewicz_at_komputronik.pl> wrote:
> Hi Daniel,
> After merge to trunk, file on disk has proper name: "file With Space.txt".
> Moreover after commit, file on my disk still has proper name, but when
> I Checkout to other directory it will have name 'file%20With%20Space.txt'.
>
> Log after second commit says exactly what was happened:
>
> A /trunk/file%20With%20Space.txt (from /branches/1.0/file With
> Space.txt:3)
>
> File in trunk was created from file in branch, but the filename was changed.
> This is unwanted behavior.

Yes, this seems unwanted. But where did it go wrong? At this point it's unclear whether this is a user error, or some tool / UI on top of SVN that did something wrong, or SVN itself.

Can you check with the person who performed that commit, to see exactly what he did? What svn operation? With what tool (and which version of the tool)?

--
Johan