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

Re: Cannot accept 'svn:sync-lock' property because it is not encoded in UTF-8

From: Dmitry Savvateev <dsavvateev_at_mail.ru>
Date: Thu, 18 Mar 2010 13:46:16 +0300

hostname is irrelevant for those not using their PCs as servers (like
me). I've been using this computer (with this hostname) for about a
year without any problems. It was used for Internet access, but only
client side.

AFAIK, Windows has a notion of "ansi" encoding, which is a single-byte
encoding for the local language used by the system (cp1251 in my
case). There are also set of "parallel" APIs returning Unicode strings
in UTF-16. May be these should be used instead, I don't know.

2010/3/18 Ryan Schmidt <subversion-2010a_at_ryandesign.com>:
> On Mar 18, 2010, at 03:47, Dmitry Savvateev wrote:
>> Yes, indeed, the host name contained cyrillics. I changed it, and the
>> problem disappeared.
>> I think, the host name was automatically generated by the system
>> (sounded like "user-pc" in Russian). That means the problem may be
>> rather common, and it makes sense to encode hostname in UTF-8 before
>> using as lock text.
> If your hostname is not UTF-8, how is Subversion to know what character encoding it's using? It seems to me it's a bug (of your OS) to present a non-UTF-8 string (or possibly even a non-ASCII string) as a valid hostname. (My thought is that if a non-ASCII hostname is desired, the UTF-8 representation of the hostname should be encoded in punycode [1] by the OS. But maybe that's just me.)
> [1] http://en.wikipedia.org/wiki/Punycode
Received on 2010-03-18 11:46:51 CET

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