I created a test database with a single file with a high-ASCII character in
the name, and I believe I've got the name to propagate all the way through
to the dump file. I'll create a branch with my changes so you can review
what's needed. I make the assumption that the XML files generated by ssphys
have the "correct" encoding for the database and that the Perl XML parser
converts this to Unicode before consumption.
The biggest headache was that DBI doesn't automatically create Unicode Perl
strings. sqlite2 by default works in UTF-8 but strings read from the DB
need to be declared as UTF-8 before use so that they're interpreted
correctly. It's also necessary to declare the cache files to be UTF-8 so
that the COPY operation receives the correct encoding.
_______________________________________________
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
