--On Monday, July 31, 2006 9:06 PM +0200 Dirk <[EMAIL PROTECTED]> wrote:
I have to admint, that I'm not very familar with the utf8 code in this branch. I just can say, that this will break the hotfixes from russia and japan to correctly convert their archives, since the fix in the utf-8 branch will only correctly convert the CP1252 into UT8 and no other codepages. The problem is, at which end we want to solve the problem. Perl comes with a full xml library and should have all possible converters installed. Relying on the converter on the ssphys will raise the complexity of the program. When we output the XML in the current codepage and indicate this in the XML header, this should be ok. It is just not that conformant to the XML spec, but it is ok. I we read the encoding from the XML file and correctly handle this in vss2svn.pl we should be able to solve most encoding issues, except those little "discouraged" character ranges specified in the XML spec.
Remember that the reason we introduced the converter was because the original code was just smashing all non-ASCII out of the output. No "conversion" was happening, but a bogus encoding was declared in the XML header. If we try to preserve the smashed characters, Perl's XML parser gets upset because of their invalid XML encoding.
Are the hotfixes you mention in the repository? I can look them over and see if there's a way to keep everybody happy.
_______________________________________________ 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
