[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: vss2svn: german umlaute (was: Subversion Tools)

From: Toby Johnson <toby_at_etjohnson.us>
Date: 2004-08-06 17:55:08 CEST

Barkey, Christian LUX wrote:

>>>I'm not sure, but I think that the locale can't be set right. The reason is
>>>that vss2svn needs to parse ss.exe output and requires that output to be in
>>>american.
>>>
>>>At the moment, vss2svn doesn't even set the locale itself, neither for calling
>>>SVN nor VSS, but requires the whole system to be switched to american...
>>>
>>>
>>>
>>>
>>If you rename the file ssde.dll in your VSS installation, American
>>status messages are output, so you shouldn't have to switch your locale. > Localization will be in the next "big" release, although that is
>>probably a couple months off.
>>
>>
>
>The ss.exe actually used is the english one. As far as I've seen the svn client
>for windows reports the error, that it is not possible to convert the german
>umlaut (neither in a filename, nor in the comment) into UTF-8. German umlaute
>in the source files are not affected.
>
>Shall I post to the vss2svn list? Or is it ok to stay here? I feel that this
>list is anyway beeing read by the vss2svn users, but not everybody reading
>the subversion-list is reading the vss2snv list.
>
>
It should really be moved to the vss2svn list because the problem is
with that script (or rather Perl maybe)? and not Subversion. I'm sorry,
I'm just one isolated American and don't know much about localization!

There are two localization issues at play here. The first, which I
referred to above, is that vss2svn must parse the output of ss.exe, and
right now it understands only English (VSS has only one "English", which
is American). But that's not your problem.

I'm 99% sure the entire problem is that vss2svn writes the VSS comments
to a tempfile before commiting because passing them on the command
prompt is too messy. And when Perl writes that tempfile, it isn't
setting its locale correctly. I know for a fact that UTF-8 wasn't fully
supported until Perl 5.8, but I don't know what I'm doing wrong (if
anything) in that Perl isn't correctly setting the locale on your
machine. Maybe *all* localization is non-existant in 5.6.

This weekend, I will release 0.3.2 with the --utf8 switch, in which all
comment files will explicitly be converted to UTF8 (and svn gets passed
"--encoding UTF-8") which solves the problem. However, as I mentioned,
this will require either that you install ActivePerl 5.8, or use the
statically-compiled version which I also will post.

There is probably some tweak to Perl or some --encoding switch that I
can pass to svn to make it work with your locale, but I don't know how
to do that. If anyone can shed some light on this then let me know!

(Please send replies to the vss2svn list, unless it has to do with the
actual svn client.)

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Aug 6 17:56:02 2004

This is an archived mail posted to the Subversion Users mailing list.