Kenneth Porter wrote:
Yep, I dug around in the VSS stuff and couldn't find anything like
that. Some googling reveals that there's some support for this in the
VSS that comes with VS2005, but I'm not rushing out to tie myself to
yet another proprietary product.
I think if any non-ASCII characters show up in the DB, it's due to
their use in filenames in the underlying filesystem. (They may also
appear in author names and check-in comments.) Does NTFS use Unicode
or the local codepage for filename characters?
In my DB I have some files with the character 0x85 in the name, which
is an elipses ("..."). The current trunk parses this properly and
generates the correct UTF-8 character in the resulting Subversion dump
file.
As you're posting from a German domain, I'm guessing you use one of
the German language codepages. Do any of your filenames intentionally
include characters from outside the 7-bit ASCII character set? Do you
use any of those characters in author names or comments?
Characters in the range 0x80-0xFF are quite common even in filenames.
Most comments were created with codepage 1252 altough I've seen a few
that use codepage 932 probably. I would not expect that these are
converted correctly. But the 0x15 character that made LOADVSSNAMES fail
did not come from a filename or comment. It's probably produced by a bug
in the name scrambling algorithm. I don't think they intended to put a
0x15 character into a 8.3 filename. What are these used for anyway?
_______________________________________________
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
