not well-formed (invalid token) at line 23, column 16, byte 835
at /usr/lib/perl5/vendor_perl/5.8.8/i386-linux-thread-multi/XML/Parser.pm
line 187
I expect that means that the input file is corrupted in some fashion? (As
opposed to a typo in the XML parser.)
Yes, I would expect this, too. Try to run the command standalone and
have a look at the XML file. Can you spot the problematic location?
There was/is some code in vss2svn to remove any invalid characters.
Possibly this is wrong with your encoding, since it probably removes
"valid" elements. Try to remove this code or extend it with the invalid
characters.
Have a special look at this line:
http://www.pumacode.org/projects/vss2svn/browser/trunk/script/vss2svn.pl#L1096
This will remove invalid windows-1252 characters. Probably this is
problematic.
Is it possible for you to run the generated XML through a XML-Checker?
While I was researching XML, I found that there are some characters
forbidden in XML, which are valid characters in some codepages. Even if
I encoded them in the "dezimal" encoding, they where reported as bad
input. So I don't know how to deal with this.
Dirk
_______________________________________________
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
