Dirk <vss2svn <at> nogga.de> writes: > Hi Constantine, > > >> "ssphys" info -eiso-8859-7 "VssAbc/data/names.dat" > > As Toby wrote, please try to run the above command standalone and > redirect to a file. > > The encoding patch is not 100% correct, and I still have no ideas, how > to make it 100% correct. We have to deal with two problems: > > 1.) different encodings: This one should be solved with the encoding > attribute, but while playing with this, I had still problems to output > characters that are allowed in one codepage, but discouraged by the XML > standard. See > http://www.w3.org/TR/REC-xml/#charsets where some characters, that are > still allowed in the the windows-1252 codepage, are discouraged in XML. > esp. most of the characters in the band [x80-x9f].
[snip] > Please have a look at your generated xml file from the names.dat and > check which character is the problematic one. Done. The culprit is a 0x92 character (reverse single apostrophe). It seems like 8859-7 is not the right encoding. Instead, "windows-1253" supports that particular character. Unfortunately, using that I get this: Couldn't open encmap windows-1253.enc: No such file or directory at /PerlApp/XML/Parser.pm line 187 It seems the like the proper encoding mapping file is not included in the exe. > Second: your output shows, that you have a missing ParserDetails.Ini > file. Please check a previous mail thread "Idiots' guide to setting up a > perl environment for vss2svn?". There is a sample ParserDetails file: Perhaps you didn't notice, but I'm using the exe. So, I guess it's also an exe generation problem. Thanks a bunch. 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
