Re: Re: [COMMITTERS] pgsql: Fixed string in German translation that causes segfault. - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: Re: [COMMITTERS] pgsql: Fixed string in German translation that causes segfault.
Date
Msg-id 1308601257.25899.5.camel@vanquo.pezone.net
Whole thread Raw
In response to Re: Re: [COMMITTERS] pgsql: Fixed string in German translation that causes segfault.  (Alvaro Herrera <alvherre@commandprompt.com>)
Responses Re: Re: [COMMITTERS] pgsql: Fixed string in German translation that causes segfault.
List pgsql-hackers
On mån, 2011-06-20 at 13:13 -0400, Alvaro Herrera wrote:
> Excerpts from Michael Meskes's message of lun jun 20 09:54:36 -0400 2011:
> > On Mon, Jun 20, 2011 at 09:15:52AM -0400, Robert Haas wrote:
> > > Yep.  Peter overrides them just before each release.
> > 
> > Aren't there better ways to implement this, like git submodules? This
> > redundancy seem awkward to me. 
> 
> There might be, but currently the translations are still using the CVS
> machinery on pgfoundry.  This stuff predates our move to Git.  It's
> possible that Peter already changed the msgstr in pgtranslation ...
> 
> Peter is working on moving that CVS stuff to Git, but AFAIR it will
> happen once 9.1 has released.

A better way might be that translators simply work on a clone of the
source repository, which is then merged (as in, git merge) at release
time.  There are some issues with that to figure out, but it sounds like
the obviously right thing, from an interface point of view.




pgsql-hackers by date:

Previous
From: Noah Misch
Date:
Subject: Re: FOR KEY LOCK foreign keys
Next
From: Magnus Hagander
Date:
Subject: Re: Re: [COMMITTERS] pgsql: Fixed string in German translation that causes segfault.