| From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
|---|---|
| To: | Daniel Gustafsson <daniel(at)yesql(dot)se> |
| Cc: | pgsql-translators(at)lists(dot)postgresql(dot)org |
| Subject: | Re: PostgreSQL misspellings in translations |
| Date: | 2019-05-28 20:36:55 |
| Message-ID: | 20190528203655.GA25214@alvherre.pgsql |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-translators |
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Daniel Gustafsson | 2019-05-28 20:41:18 | Re: PostgreSQL misspellings in translations |
| Previous Message | Daniel Gustafsson | 2019-05-28 15:26:27 | PostgreSQL misspellings in translations |