Ori Avtalion wrote:
Hi,
Any chance of progress on this problem?
Dirk wrote:
Hello Ferry,
I have analyzed the problem and this is one of the cases that I don't
know how to handle. I have removed all private information and will post
this answer publically.
The reason is, that you have a garbaged record in your database. The
problem is, that one of the garbaged cacharcters is 12d or 0x0c, the
letter "FF" in the windows-1252 or ANSI codepage.This character is
passed through unchanged since it is only a "space control character".
No the big question: How to deal with the situation?
1.) Does analyze detect this problem and fix the broken record?
2.) Shall we exclude the character from beeing outputted within "ssphys"?
3.) Shall we filter the character in vss2svn?
As a workaround you can modify the line 1105 in vss2svn.pl [1] to also
include the "x0c" character.
$gSysOut =~
s/[\x00-\x09\x0c\x11\x12\x14-\x1F\x81\x8D\x8F\x90\x9D]/_/g; # just to be
sure
But what is the general solution?
Best regards
Dirk
[1]
http://www.pumacode.org/projects/vss2svn/browser/trunk/script/vss2svn.pl#L1105
I have tried the workaround other some other avenues but unfortunately it
appears that the database I was trying to convert is so bloody corrupt that not
even the M$ tooling can correct the problems and today(!) we switched to TFS
(company policy.........). thanks for your help though!
_______________________________________________
vss2svn-users mailing list
Project homepage:
http://www.pumacode.org/projects/vss2svn/
Subscribe/Unsubscribe/Admin:
http://lists.pumacode.org/mailman/listinfo/vss2svn-users-lists.pumacode.org
Mailing list web interface (with searchable archives):
http://dir.gmane.org/gmane.comp.version-control.subversion.vss2svn.user
