ok...
I've try your proposal and the aux file is corrupted too.
That has make me think that the problem is in the locale used by the perl instance executing scmbug.
I've tried this inside Subversion.pm
    `locale > /tmp/txt2 `;

And this is what I get!!!
mistral:~/kk# cat /tmp/txt2
LANG=
LC_CTYPE="POSIX"
LC_NUMERIC="POSIX"
LC_TIME="POSIX"
LC_COLLATE="POSIX"
LC_MONETARY="POSIX"
LC_MESSAGES="POSIX"
LC_PAPER="POSIX"
LC_NAME="POSIX"
LC_ADDRESS="POSIX"
LC_TELEPHONE="POSIX"
LC_MEASUREMENT="POSIX"
LC_IDENTIFICATION="POSIX"
LC_ALL=


That is the problem!

I've tried a little "program" in perl to test if the problem is in my perl config (if any) or somewhere in scmbug config and it seems it's in scmbug:
mistral:~/kk# cat perltest
#!/usr/bin/perl

`locale >kk.txt`
mistral:~/kk# perl perltest
mistral:~/kk# cat kk.txt
LANG=es_ES.UTF-8
LANGUAGE=es_ES.UTF-8:[EMAIL PROTECTED]:es_ES:es:en_GB:en
LC_CTYPE="es_ES.UTF-8"
LC_NUMERIC="es_ES.UTF-8"
LC_TIME="es_ES.UTF-8"
LC_COLLATE="es_ES.UTF-8"
LC_MONETARY="es_ES.UTF-8"
LC_MESSAGES="es_ES.UTF-8"
LC_PAPER="es_ES.UTF-8"
LC_NAME="es_ES.UTF-8"
LC_ADDRESS="es_ES.UTF-8"
LC_TELEPHONE="es_ES.UTF-8"
LC_MEASUREMENT="es_ES.UTF-8"
LC_IDENTIFICATION="es_ES.UTF-8"
LC_ALL=


So we only need to know where the locale is changed and why...
I think that Glue is used by Subversion, and subversion is used by apache2 (in my system I use https to access my reps) so the problem can be in apache2 using the incorrect locale (???) I remember I read something about that in the past...

In any case, I've tested this:

    open ( SVNLOOK_INFO, "env LANG=es_ES.UTF-8 LANGUAGE=es_ES.UTF-8 svnlook info " . $svn_tools_argument . "\
 $svn_txn $svn_repository |" );

(only added the env command to the original line)

and...

IT WORKS!!!!!!!!

$VAR1 = 'bug 26: Añado una linea a fich2 y pruebo el tema de los acentos camión, ALÁ, ñiñli
';

It has been hard to hunt but we got it!
Now we "only" nedd to know how to make this more generic...
Perhaps can you put a command in yout scripts to get the locale from some of the config files and set the new environment at the begining of the script??
I leave that to you... I don't know very much about what I'm talking :-)


Kristis Makris wrote:
On Thu, 2006-12-14 at 22:38 +0100, Javier Lafuente wrote:

  
This is very strange... It's corrupted in the file read becouse, as I
previously said, I get the right output when I issue the same command:
    

Yes, this is strange.

  
mistral:~# svnlook info -r 30 /var/svn-repos/test_rep_a
javi
2006-12-14 22:35:23 +0100 (jue, 14 dic 2006)
87
bug 26: Añado una linea a fich2 y pruebo el tema de los acentos
camión, ALÁ, ñiñli


Anything else to try?
    

Sure.

How about instead of reading the output of svnlook from a pipe we save
it first in a file, and then read the file ?

my $cmd = "svnlook info " . $svn_tools_argument . " $svn_txn
$svn_repository";
`$cmd > /tmp/txt`;
open ( SVNLOOK_INFO, "<:encoding(UTF-8)", "/tmp/txt" );

Then have a look at /tmp/txt to see if at least the output of svnlook
info is not corrupted in it, and then see if what was read from the file
was not corrupted.

I'm trying to see if the pipe is causing this. It probably isn't. It's
probably some other Perl issue. As if we are not reading the encoding
right.


  
_______________________________________________
scmbug-users mailing list
[email protected]
http://lists.mkgnu.net/cgi-bin/mailman/listinfo/scmbug-users

Reply via email to