Am 16.05.2014 15:14, schrieb Simon Large:
> On 16 May 2014 11:57, Sven <sven.koehler_at_gmail.com> wrote:
>> Today, I tried to use the SVN command line client from within TexStudio.
>> TexStudio invoked svn.exe with the following parameters:
>> svn.exe up --non-interactive c:\path_with_hebrew_letters\somefile.txt
>> The result was:
>> Skipped 'c:\path_with_hebrew_letters\somefile.txt'
>> Summary of conflicts:
>> Skipped paths: 1
>> As you can imagine, that's not very satisfying.
>> I then investigated. I opened a command prompt (cmd.exe, which is
>> unicode aware), and then tried the same command as TexStudio executed.
>> The result was the same (skipped path ...). As a workaround, I can "cd"
>> into the directory, and then use the command "svn up somefile.txt".
>> Another workaround is to renaming the folder with the hebrew characters.
>> My conclusion is that the svn command line client that ships with
>> tortoise SVN does not properly (if at all) support windows'
>> unicode-based path names.
>> I should mention that I was using Tortoise SVN 1.8.7.
> Hi Sven,
> Although the svn.exe you used was bundled with TSVN, the code for it
> comes from the core subversion project so you would need to report the
> issue on users at subersion.apache.org
Then again, it could simply be an issue with how you compile the
sources. You may know that the Windows API exists in two flavors, one
using the good old 8bit per character and one using 16bit per character
and it takes some defines/compiler switches to switch between them.
So they will probably ask me which options you use for configure of
subversion, apr, etc. - or are you using VisualStudio? Well, my point is
that I really don't know these details.
I'm really the wrong guy to report the issue to the subversion developers.
> I'm assuming you don't see this issue with the TSVN GUI tools.
No, the GUI tools are fine.
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2014-05-16 14:35:33 CEST