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

If files in db/revprops/ are GBK encoding will cause mod_dav_svn REPORT failed?

From: LiuYan 刘研 <lovetide_at_21cn.com>
Date: Wed, 17 Nov 2010 11:48:07 +0000 (UTC)

I converted CVSNT respositoy to SVN repository some days ago, and config
mod_dav_svn in Apache http.conf.

When I try 'svn log', it shown some logs but
failed/terminated at some revisions with a message like:
svn: REPORT of '/svn/cmcc/!svn/bc/1': 200 OK (

I try to the svn:// protocol to get log of the failed revisions, it can get the
log, but the log is not human-readable like the following:
svn log svn:// -r 1
r1 | (no author) | 2005-11-10 17:28:50 +0800 (星期四, 10 十一月 2005) | 2 lines

Standard project directories initialized by cvs2svn.?\211?\201 cvs2svn

It seems a charset encoding problem of 'revprops' files because I
set 'ctx.initial_project_commit_message' cvs2svn options config file to a
string contains Chinese characters, and cvs2svn options config file itself is
encode in GBK, and it seems cvs2svn does not converted the charset encoding of
initial_project_commit_message to UTF-8.

Does this encoding issue can caused mod_dav_svn REPORT failed?
Received on 2010-11-17 12:49:06 CET

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.