...Summary...
attached mail follows:
Good at #svn people told me to edit ~/.subversion/config to solve my problem.
So now the config includes 'log-encoding = koi8-r'
but the exactly error message appears when I trying to import/commit.
Note: LOCAL set to "C", and I don't like to set it to koi8-r or
something else, cuz I like to see all messages from applications in english.
Is there any way to log non-ascii messages without setting LOCALE into
koi8-r codepage(I did try it, but people say it should fix the problem)?
attached mail follows:
http://subversion.tigris.org/issues/show_bug.cgi?id=1480
Summary: svn commit: russian chars(koi8-r) in log forces
commit failure
Component: subversion
Version: current
Platform: PC
URL:
OS/Version: FreeBSD
Status: NEW
Status Whiteboard:
Keywords:
Resolution:
Issue type: DEFECT
Priority: P3
Subcomponent: unknown
AssignedTo: issues@subversion
ReportedBy: alter
svn commit: russian chars(koi8-r) in log forces commit failure;
english chars pass well.
shell script to reproduse:
svnadmin create /usr/local/svn/repos1
mkdir ~/work && touch ~/work/file
cd ~/work
svn import file:///usr/local/svn/repos1 // with log message in
russian(koi8-r codepage) [you can replay with any non-ascii chars, I
think] cousing:
"svn-commit.tmp" 4 lines, 63 characters
svn: Invalid argument
svn: failure during string recoding
svn: Your commit message was left in a temporary file:
svn: 'svn-commit.tmp'
// if log message in ascii codepage, all is fine.
// btw, the same applyed to 'svn commit'
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Aug 20 14:54:42 2003