pg.ddx.io pgsql-translators@postgresql.org mailing list archive
help / color / mirror / Atom feedPostgreSQL misspellings in translations
3+ messages / 2 participants
[nested] [flat]
* PostgreSQL misspellings in translations
@ 2019-05-28 15:26 Daniel Gustafsson <daniel@yesql.se>
2019-05-28 20:36 ` Re: PostgreSQL misspellings in translations Alvaro Herrera <alvherre@2ndquadrant.com>
0 siblings, 1 reply; 3+ messages in thread
From: Daniel Gustafsson @ 2019-05-28 15:26 UTC (permalink / raw)
To: pgsql-translators@lists.postgresql.org
Spotted two misspellings of PostgreSQL in the translations as per the attached
patch.
cheers ./daniel
Attachments:
postgressql.patch (application/octet-stream, 1.7K) download
From 69141960f1cfefc13efcece5a7b2f5d5477ce68b Mon Sep 17 00:00:00 2001
From: Daniel Gustafsson <daniel@yesql.se>
Date: Tue, 28 May 2019 11:14:39 -0400
Subject: [PATCH] Fix misspellings of PostgreSQL in translations
---
src/bin/scripts/po/sv.po | 2 +-
src/interfaces/ecpg/preproc/po/pt_BR.po | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/src/bin/scripts/po/sv.po b/src/bin/scripts/po/sv.po
index 6dd3c803d0..c8ee579277 100644
--- a/src/bin/scripts/po/sv.po
+++ b/src/bin/scripts/po/sv.po
@@ -1173,7 +1173,7 @@ msgstr ""
#~ msgstr "%s: Växeln \"freeze\" kan inte utföras med enbart analys.\n"
#~ msgid "cannot use the \"%s\" option on server versions older than PostgreSQL 12"
-#~ msgstr "flaggan \"%s\" kan inte användas på serverversioner äldre än PostgresSQL 12"
+#~ msgstr "flaggan \"%s\" kan inte användas på serverversioner äldre än PostgreSQL 12"
#~ msgid "cannot use the \"%s\" option on server versions older than PostgreSQL 9.6"
#~ msgstr "flaggan \"%s\" kan inte användas på serverversioner äldre än PostgreSQL 9.6"
diff --git a/src/interfaces/ecpg/preproc/po/pt_BR.po b/src/interfaces/ecpg/preproc/po/pt_BR.po
index f64ecaeec4..dc632f30e5 100644
--- a/src/interfaces/ecpg/preproc/po/pt_BR.po
+++ b/src/interfaces/ecpg/preproc/po/pt_BR.po
@@ -447,7 +447,7 @@ msgstr "esperado \"@\", encontrado \"%s\""
#: preproc.y:13993
#, c-format
msgid "only protocols \"tcp\" and \"unix\" and database type \"postgresql\" are supported"
-msgstr "somente os protocolos \"tcp\" e \"unix\" e tipo banco de dados \"postgressql\" sãosuportados"
+msgstr "somente os protocolos \"tcp\" e \"unix\" e tipo banco de dados \"postgresql\" sãosuportados"
#: preproc.y:13996
#, c-format
--
2.14.1.145.gb3622a4ee
=
* Re: PostgreSQL misspellings in translations
2019-05-28 15:26 PostgreSQL misspellings in translations Daniel Gustafsson <daniel@yesql.se>
@ 2019-05-28 20:36 ` Alvaro Herrera <alvherre@2ndquadrant.com>
2019-05-28 20:41 ` Re: PostgreSQL misspellings in translations Daniel Gustafsson <daniel@yesql.se>
0 siblings, 1 reply; 3+ messages in thread
From: Alvaro Herrera @ 2019-05-28 20:36 UTC (permalink / raw)
To: Daniel Gustafsson <daniel@yesql.se>; +Cc: pgsql-translators@lists.postgresql.org
On 2019-May-28, Daniel Gustafsson wrote:
> Spotted two misspellings of PostgreSQL in the translations as per the attached
> patch.
FTR, any translation entry prefixed with #~ corresponds to an obsolete
one, that is, a string that once was a valid message in the catalog and
was translated in that catalog, but isn't a valid message anymore. It
would be picked up by the fuzzy matcher if the string is revived in the
code, but I wouldn't normally bother trying to get a fix for it
committed. If anything, I would remove all #~ entries from the catalog
files once in a while ...
--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
^ permalink raw reply [nested|flat] 3+ messages in thread
* Re: PostgreSQL misspellings in translations
2019-05-28 15:26 PostgreSQL misspellings in translations Daniel Gustafsson <daniel@yesql.se>
2019-05-28 20:36 ` Re: PostgreSQL misspellings in translations Alvaro Herrera <alvherre@2ndquadrant.com>
@ 2019-05-28 20:41 ` Daniel Gustafsson <daniel@yesql.se>
0 siblings, 0 replies; 3+ messages in thread
From: Daniel Gustafsson @ 2019-05-28 20:41 UTC (permalink / raw)
To: Alvaro Herrera <alvherre@2ndquadrant.com>; +Cc: pgsql-translators@lists.postgresql.org
> On 28 May 2019, at 16:36, Alvaro Herrera <alvherre@2ndquadrant.com> wrote:
>
> On 2019-May-28, Daniel Gustafsson wrote:
>
>> Spotted two misspellings of PostgreSQL in the translations as per the attached
>> patch.
>
> FTR, any translation entry prefixed with #~ corresponds to an obsolete
> one, that is, a string that once was a valid message in the catalog and
> was translated in that catalog, but isn't a valid message anymore. It
> would be picked up by the fuzzy matcher if the string is revived in the
> code, but I wouldn't normally bother trying to get a fix for it
> committed. If anything, I would remove all #~ entries from the catalog
> files once in a while …
Ah, right. I reacted to it since it was committed only recently.
cheers ./daniel
^ permalink raw reply [nested|flat] 3+ messages in thread
end of thread, other threads:[~2019-05-28 20:41 UTC | newest]
Thread overview: 3+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2019-05-28 15:26 PostgreSQL misspellings in translations Daniel Gustafsson <daniel@yesql.se>
2019-05-28 20:36 ` Alvaro Herrera <alvherre@2ndquadrant.com>
2019-05-28 20:41 ` Daniel Gustafsson <daniel@yesql.se>
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox