From: Alvaro Herrera <alvherre@2ndquadrant.com>
To: Daniel Gustafsson <daniel@yesql.se>
Cc: pgsql-translators@lists.postgresql.org
Subject: Re: PostgreSQL misspellings in translations
Date: Tue, 28 May 2019 16:36:55 -0400
Message-ID: <20190528203655.GA25214@alvherre.pgsql> (raw)
In-Reply-To: <532270F8-FFC3-4831-AFB3-57110DF74E25@yesql.se>
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-translators@postgresql.org
Cc: alvherre@2ndquadrant.com, daniel@yesql.se, pgsql-translators@lists.postgresql.org
Subject: Re: PostgreSQL misspellings in translations
In-Reply-To: <20190528203655.GA25214@alvherre.pgsql>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
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