Re: Encoding problems using git-svn

From: Robin Rosenberg <robin.rosenberg@dewire.com>
Date: Nov 2, 2008, 13:45 UTC
Message-ID: <200811021445.37149.robin.rosenberg@dewire.com>
In-Reply-To: <20081102094845.GB16003@untitled>

On söndag 02 november 2008 10:48 Eric Wong wrote:

Show 20 quoted lines

> James North <tocapicha@gmail.com> wrote:
> > 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).

"Most" people don't have a legacy encoding problem, but some of us do and tools that help with migration by enforcing UTF-8 internally help. SVN is such an example, though not very helpful as an SCM. That way we can still use legacy encodings for old stupid tools until we can move to an all UTF-8 world. We're not there yet, but in a few years hopefully. That's when it's sad that the git command line for example still enforce the legacy encoding. Some GUI's, like git gui, jgit and probably a few others help by recoding when necessary.

-- robiin