Re: Encoding problems using git-svn

From: Eric Wong <normalperson@yhbt.net>
Date: Nov 2, 2008, 09:48 UTC
Message-ID: <20081102094845.GB16003@untitled>
In-Reply-To: <8b168cfb0810300814i53a264c2x997543e145d5e15a@mail.gmail.com>

James North <tocapicha@gmail.com> wrote:

Show 8 quoted lines

> Hi Eric,
> 
> Don't worry about not seeing the patch and thanks for the answer :)
> 
> Your patch works great.
> 
> Messages appear without problems on "svn log" and "git log", I haven't
> found any gotcha that I know of.

Thanks for the confirmation.

> The weird thing is that this problem was not found by anyone before, I
> guessed there should be some people with a setup similar to mine.

Squeaky wheel gets the grease :)

Honestly, I think most folks have just moved onto UTF-8 entirely and left legacy encodings behind. Especially people using modern tools like git (along with SVN enforcing UTF-8 at the repository/protocol level).

Junio:

I've pushed the following out to git://git.bogomips.org/git-svn.git:

Eric Wong (2):
      git-svn: don't escape tilde ('~') for http(s) URLs
      git-svn: respect i18n.commitencoding config

I'll try to get around to the more robust escaping checks and splitting out the monolithic git-svn.perl source next week.

-- 
Eric Wong