Following-up on my old problem (search for "Non-1252 (?) paths/filenames in VSS are not handled properly"), I tried the aforementioned nightly and I got this:
C:\Dev\VSS>vss2svn --vssdir VssAbc --encoding="iso-8859-7" --verbose could not find ParserDetails.ini in /PerlApp/XML/SAX Connecting to database ./_vss2svn/vss_data.db ======== VSS2SVN ======== BEGINNING CONVERSION... Start Time : Fri Feb 2 17:27:49 2007 VSS Dir : VssAbc Temp Dir : ./_vss2svn Dumpfile : vss2svn-dumpfile.txt VSS Encoding : iso-8859-7 VSS2SVN ver : 0.11.0-nightly.287 SSPHYS exe : ssphys SSPHYS ver : 0.22.0.275 XML Parser : XML::SAX::Expat TASK: INIT SETTING TASK LOADVSSNAMES SETTING STEP 0 TASK: LOADVSSNAMES "ssphys" info -eiso-8859-7 "VssAbc/data/names.dat" not well-formed (invalid token) at line 13842, column 33, byte 478724 at /PerlApp/XML/Parser.pm line 187 I really need to test the encoding fix. Is there another way to get a correct build? Doc _______________________________________________ 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
