Great job guys... perhaps we should make those files available in the contrib area? Or perhaps the author of XML::Encoding would be interested in them?
That was exactly the type of problem I wanted to avoid by transferring the responsibility for the transcoding from ssphys to vss2svn. I expected, since PERL comes with an expat parser, that it also has the full set of encoding tables already available. So I don't wanted to depend on the need for iconv. This would have complicated things even further.
Ok, since the day we started with all this encoding issues, I have learned a bit and today I know that windows has a built in conversion function also to convert from any codepage to UTF8 via the NarrowStringToWideString API. For Linux we could have used libiconv. So It would have been possible to do the full conversion on the ssphys side, without much overhead.
Nevertheless writing the encoding table wasn't rocket science. I simply did, what was sepcified in the README. But naturally documentation is good and we should document everything we have. I will update the WIKI.
@Constantine: It is good to hear, that it worked. Good luck with the rest of the conversion.
Best regards 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
