--On Thursday, August 03, 2006 1:26 AM +0200 Dirk <[EMAIL PROTECTED]> wrote:

I used the setlocale once in the software, when I tried to filter only
printeable characters of the elements in respect to the current codepage.
But that was all.

True, I think that's all it's used for, and I think that's already done in TinyXML. It uses isprint() to determine what to toss, and that in turn depends on the current locale. So we could just bypass that line of code and output everything, and trust the Perl XML parser to barf on any invalid characters when reading those strings in. We don't need the sanitizer in XML.cpp.

So the only real need is to know what to put in the XML encoding string. We could either pass that in on the command line or query it from the environment. For Windows, assuming you're converting on a machine that's used the VSS DB, the machine's locale will be set to the correct code page, and you just need to cook up a matching XML encoding string (presumably using GetACP). For Linux (which was never involved in VSS), you need to somehow pass in the encoding to use. I'd suggest making this a parameter to ssphys and passing it through from vss2svn.
_______________________________________________
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

Reply via email to