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

SVN Log gotcha...

From: James Moger <James.Moger_at_TRANSONIC.com>
Date: 2004-05-11 22:35:03 CEST

I recently converted a repository from P4 to SVN. I have discovered that some of my imported log messages have characters like 0x96 that make the UTF-8 XML log message retrieval unhappy (but committing the message apparently worked). Here is an example error output:

svn log http://odin/svn/trunk/java_unstable -r 264
svn: REPORT request failed on '/svn/!svn/bc/264/trunk/java_unstable'
svn: The REPORT request returned invalid XML in the response: XML parse error at
 line 8: not well-formed (invalid token) (/svn/!svn/bc/264/trunk/java_unstable)

Further investigation showed that those invalid characters are in my Perforce depot too. Turns out one of the developers sometimes creates log messages/changelist comments with Word and then pastes them in - apparently some control or hidden characters must have been copied & pasted.

Just figured I would pass on that experience in case anyone else happens to stumble across that problem too.

Perhaps the svn client could fail with more details or maybe it could limp along and drop questionable characters?

Related to this...Is there a way to modify/edit a log message?
I haven't found one yet so the plan is to either redo the dump process (ugh) or try to edit the dump file to save time.


To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue May 11 22:35:39 2004

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.