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

Re: Bug: pre-commit rejection message character encoding

From: Stefan Küng <tortoisesvn_at_gmail.com>
Date: Fri, 14 Aug 2009 20:55:29 +0200

On 12.08.2009 12:16, Anders Munch wrote:

>> Can't you verify this with the svn command line client?
> That's not so easy: The CL client has no way of displaying Unicode
> directly, it must spit out bytes; whether these bytes are correct or
> not depends on which encoding they were supposed to be in. But I
> don't know which encoding they are supposed to be in; there's no
> switch to request a specific encoding, and I know of no documentation
> on what sort of guessing-game the CL client uses to choose an
> encoding. To make things worse, sometimes it spits out strange,
> undocumented escape sequences like \?123 which noone seems to know
> what to make of.
> I can't demonstrate faulty behaviour when I don't know what the
> intended behaviour is.

the CL client uses the system codepage for the encoding, because that's
what the console is using.
Now, those escape sequences like \?123 appear if a char can't be shown
in the current codepage. So it shows the utf8 char 'number' instead.

But according to the svn API docs, all svn APIs always return and accept
strings/data only in utf8. So that's what TSVN is doing.


   oo  // \\      "De Chelonian Mobile"
  (_,\/ \_/ \     TortoiseSVN
    \ \_/_\_/>    The coolest Interface to (Sub)Version Control
    /_/   \_\     http://tortoisesvn.net
To unsubscribe from this discussion, e-mail: [dev-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2009-08-14 20:55:53 CEST

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