Thread: Call for translations

Some of you have already been doing a great job, but I would like to point out
that with the upcoming release of PostgreSQL 8.3, it is once again time to
update the message translations.  We are now near a string freeze, which has
traditionally been associated with the first release candidate, so it's a
good time to do this work now.

If you want to help, see <http://pgtranslation.projects.postgresql.org/> for
instructions and other information.  If there are already active translation
teams, please communicate with them first.  The mailing list
<pgtranslation-translators@pgfoundry.org> is available for general discussion
and coordination of translation activities.

--
Peter Eisentraut
http://developer.postgresql.org/~petere/

Peter Eisentraut wrote:
> Some of you have already been doing a great job, but I would like to point out
> that with the upcoming release of PostgreSQL 8.3, it is once again time to
> update the message translations.  We are now near a string freeze, which has
> traditionally been associated with the first release candidate, so it's a
> good time to do this work now.

I would like to propose this patch.  This avoids an inconsistent message
wording, and removes the need to translate a string by duplicate.

--
Alvaro Herrera                               http://www.PlanetPostgreSQL.org/
"Estoy de acuerdo contigo en que la verdad absoluta no existe...
El problema es que la mentira sí existe y tu estás mintiendo" (G. Lama)