pgsql: Translation updates.
Log Message:
-----------
Translation updates.
Tags:
----
REL8_3_STABLE
Modified Files:
--------------
pgsql/src/backend/po:
de.po (r1.29.2.1 -> r1.29.2.2)
(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/po/de.po?r1=1.29.2.1&r2=1.29.2.2)
es.po (r1.15.2.1 -> r1.15.2.2)
(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/po/es.po?r1=1.15.2.1&r2=1.15.2.2)
fr.po (r1.18.2.1 -> r1.18.2.2)
(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/po/fr.po?r1=1.18.2.1&r2=1.18.2.2)
pgsql/src/bin/initdb/po:
fr.po (r1.14 -> r1.14.2.1)
(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/bin/initdb/po/fr.po?r1=1.14&r2=1.14.2.1)
pgsql/src/bin/pg_config/po:
fr.po (r1.9 -> r1.9.2.1)
(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/bin/pg_config/po/fr.po?r1=1.9&r2=1.9.2.1)
pgsql/src/bin/pg_controldata/po:
es.po (r1.10.2.1 -> r1.10.2.2)
(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/bin/pg_controldata/po/es.po?r1=1.10.2.1&r2=1.10.2.2)
fr.po (r1.15 -> r1.15.2.1)
(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/bin/pg_controldata/po/fr.po?r1=1.15&r2=1.15.2.1)
pgsql/src/bin/pg_ctl/po:
cs.po (r1.2 -> r1.2.10.1)
(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/bin/pg_ctl/po/cs.po?r1=1.2&r2=1.2.10.1)
fr.po (r1.12 -> r1.12.2.1)
(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/bin/pg_ctl/po/fr.po?r1=1.12&r2=1.12.2.1)
pgsql/src/bin/pg_dump/po:
fr.po (r1.16 -> r1.16.2.1)
(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/bin/pg_dump/po/fr.po?r1=1.16&r2=1.16.2.1)
pgsql/src/bin/pg_resetxlog/po:
fr.po (r1.11 -> r1.11.2.1)
(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/bin/pg_resetxlog/po/fr.po?r1=1.11&r2=1.11.2.1)
pgsql/src/bin/psql/po:
es.po (r1.16.2.1 -> r1.16.2.2)
(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/bin/psql/po/es.po?r1=1.16.2.1&r2=1.16.2.2)
fr.po (r1.22 -> r1.22.2.1)
(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/bin/psql/po/fr.po?r1=1.22&r2=1.22.2.1)
pgsql/src/bin/scripts/po:
fr.po (r1.15 -> r1.15.2.1)
(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/bin/scripts/po/fr.po?r1=1.15&r2=1.15.2.1)
pgsql/src/interfaces/libpq/po:
fr.po (r1.17 -> r1.17.2.1)
(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/interfaces/libpq/po/fr.po?r1=1.17&r2=1.17.2.1)
Tom Lane wrote:
Translation updates.
Tags:
----
REL8_3_STABLE
Hmm, there's something weird about this update ... apparently the
spanish files were updated but the diff shows up empty. Investigating.
--
Alvaro Herrera http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
Alvaro Herrera wrote:
Tom Lane wrote:
Translation updates.
Tags:
----
REL8_3_STABLEHmm, there's something weird about this update ... apparently the
spanish files were updated but the diff shows up empty. Investigating.
Well, apparently nobody updated the file in the pgtranslation CVS, so
it's OK that nothing happened. I'm baffled about $PostgreSQL$ being
unexpanded yet though. Good thing we have a $Id$ that keeps current
with the pgtranslation repo. Maybe it's $PostgreSQL$ that's causing the
empty diff to show up.
--
Alvaro Herrera http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.
Alvaro Herrera <alvherre@commandprompt.com> writes:
Hmm, there's something weird about this update ... apparently the
spanish files were updated but the diff shows up empty. Investigating.
Well, apparently nobody updated the file in the pgtranslation CVS, so
it's OK that nothing happened.
Don't scare me like that :-(. This is the first time I've done the
translation commits and I was sure I'd blown it somehow.
I'm baffled about $PostgreSQL$ being
unexpanded yet though. Good thing we have a $Id$ that keeps current
with the pgtranslation repo. Maybe it's $PostgreSQL$ that's causing the
empty diff to show up.
Hmm, you're right, the es/postgres.po file in the pgtranslation
repository has an unexpanded $PostgreSQL$ tag. Which is unsurprising
since pgfoundry's CVS is probably not set to recognize that tag.
The cp-po script is supposed to ignore that when comparing the files,
but it looks like there's something wrong with its regexp. Don't
quite see what though ... oh, yeah I do: it's assuming there will
be a colon after the keyword. Don't have commit on that repository,
or I'd go fix it ...
regards, tom lane
Tom Lane wrote:
Alvaro Herrera <alvherre@commandprompt.com> writes:
Hmm, there's something weird about this update ... apparently the
spanish files were updated but the diff shows up empty. Investigating.Well, apparently nobody updated the file in the pgtranslation CVS, so
it's OK that nothing happened.Don't scare me like that :-(. This is the first time I've done the
translation commits and I was sure I'd blown it somehow.
Sorry :-)
I'm baffled about $PostgreSQL$ being
unexpanded yet though. Good thing we have a $Id$ that keeps current
with the pgtranslation repo. Maybe it's $PostgreSQL$ that's causing the
empty diff to show up.Hmm, you're right, the es/postgres.po file in the pgtranslation
repository has an unexpanded $PostgreSQL$ tag. Which is unsurprising
since pgfoundry's CVS is probably not set to recognize that tag.
Well, my intention was that $Id$ should be expanded in pgfoundry, and
$PostgreSQL$ should be expanded when the file is imported from pgfoundry
into the main CVS repo. I'm not sure why it hasn't.
The cp-po script is supposed to ignore that when comparing the files,
but it looks like there's something wrong with its regexp. Don't
quite see what though ... oh, yeah I do: it's assuming there will
be a colon after the keyword. Don't have commit on that repository,
or I'd go fix it ...
OK, fix committed (I just removed the colon in the regexp). Thanks.
--
Alvaro Herrera http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
Alvaro Herrera <alvherre@commandprompt.com> writes:
Tom Lane wrote:
Hmm, you're right, the es/postgres.po file in the pgtranslation
repository has an unexpanded $PostgreSQL$ tag. Which is unsurprising
since pgfoundry's CVS is probably not set to recognize that tag.
Well, my intention was that $Id$ should be expanded in pgfoundry, and
$PostgreSQL$ should be expanded when the file is imported from pgfoundry
into the main CVS repo. I'm not sure why it hasn't.
Right, but the copy in pgfoundry has never been imported into the main
CVS repo ...
regards, tom lane