Re: merge issue (solved) - 1.1.1 client, 1.0.8 server
From: Robert Spier <rspier_at_pobox.com>
Date: 2004-11-21 11:53:35 CET
> > I think I might have a 1.0/1.1 compatibility issue.
Yay! (Well, not-Yay! for having the control character that leaked over
> See that character after "has now been tagged" ? I think that's the
Confirmed. After editing the log message, 1.1.1 is quite happy to
Is reason this problem exists with 1.1.1 and not the 1.0.8 client is
In general, I've found that many (all?) of my odd SVN problems have
Do you have any suggestions for better debugging these issues before
Clkao wrote the (below) script for checking encodings. It would be
Thanks-
-R
--- # Clkao's log message re-encoder (changes log messages improperly # encoded as latin-1 to UTF-8) use SVN::Fs; use Encode; use Encode::Guess; my $repospath = shift or die 'no repospath'; my $repos = SVN::Repos::open ($repospath) or die $!; my $fs = $repos->fs; my $yrev = $fs->youngest_rev; my $pool = SVN::Pool->new_default; for (0..$yrev) { $pool->clear; my $log = $fs->revision_prop ($_, 'svn:log'); my $enc = guess_encoding ($log, qw/latin-1/); next unless ref ($enc); warn "log at $_ is ".$enc->name; next if $enc-name eq "utf-8"; Encode::from_to ($log, $enc->name, 'utf-8'); $fs->change_rev_prop ($_, 'svn:log', $log); } --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org For additional commands, e-mail: dev-help@subversion.tigris.orgReceived on Sun Nov 21 11:55:06 2004 |
This is an archived mail posted to the Subversion Dev mailing list.
This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.