Kenneth Porter schrieb:
I'm trying to use ssphys from the trunk instead of ssphys_utf8 and I'm
trying to force the XML to use a locale.
Hi Kenneth,
thank you for all the support on the "i18n" side of ssphys. Just a dump
question: why do we need this setlocale thing? Only to query the cp
identifier? I don't want to picky on this thing, but isn't the problem
on a different side?
* VSS encodes the data in the current users codepage.
* ssphys reads "unsigned chars" regardless of the encoding and writes
"unsigned chars" to an XML file, also regardless of the encoding. We
could also you a binary mode here.
* ssphys also places the "users codepage" into the header of the xml
--> Problem xml defines some discouraged characters that can be part of
a codepage
* vss2svn slurps the xml file
* it detects the encoding
* it sets the internal encoding to the encoding read from the xml file
* it converts from the encoding to utf-8
I don't see, that we need the setlocale thing in this flow. We only need
to specify the codepage used in vss in the xmlheader.
Or is setting the locale important on linux to correctly output characters?
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.
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
