[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: command line client has problems with paths with hebrew characters

From: Sven <sven.koehler_at_gmail.com>
Date: Fri, 16 May 2014 19:26:02 +0300

Am 16.05.2014 19:17, schrieb Stefan Küng:
> On 16.05.2014 18:12, Sven wrote:
>> Am 16.05.2014 18:57, schrieb Stefan Küng:
>>> On 16.05.2014 12:57, Sven wrote:
>>>> Hi,
>>>>
>>>> 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.
>>>
>>> if you get "Skipped 'c:\path_with_hebrew_letters\somefile.txt'" and the
>>> chars you see there are the correct ones, then that implies that svn.exe
>>> is unicode aware.
>>
>> They are the correct ones. At least in TexStudio. The Windows console is
>> not awfully good at displaying hebrew characters.
>
> You said that cmd.exe is unicode aware. If it is then it can show those
> characters just fine. Only if it isn't then it can't show those characters.

Not if the fonts don't contain them.

>> Also, how can you know how svn internally processes the paths? Even if
>> it manages to printing the folder name without mangling it up, it
>> doesn't mean that it is properly passed down the calls.
>
> Because every path passed to svn is converted to utf8 on input and only
> utf8 strings are passed around internally in the svn lib.
>
> Also the fact that it works if you 'cd' into that dir clearly shows that
> svn.exe can deal with such paths, because not only are the paths
> converted to utf8 on input but also all relative paths are first
> converted to full absolute paths before they're passed to the internal
> svn functions.

If you cd into the directory, then svn probably deals with relative
paths only. Inside the folder, there are not filenames with hebrew
characters.

>> Basically, the "Skipping ..." message means, that svn thinks the file
>> doesn't exist.
>
> Nope. Skipping simply means the file was skipped. There can be other
> reasons a file is skipped.

True. My fault. Let me put it the other way round: If a file doesn't
exist, then svn also prints the "Skipping ..." message.

------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=3078525

To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2014-05-16 18:20:52 CEST

This is an archived mail posted to the TortoiseSVN Users mailing list.