| From: | Daniel Gustafsson <daniel(at)yesql(dot)se> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
| Cc: | pgsql-translators(at)lists(dot)postgresql(dot)org |
| Subject: | Re: PostgreSQL misspellings in translations |
| Date: | 2019-05-28 20:41:18 |
| Message-ID: | 59E90A88-D61D-4936-A846-10EB1E690077@yesql.se |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-translators |
> On 28 May 2019, at 16:36, Alvaro Herrera <alvherre(at)2ndquadrant(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2019-06-04 21:34:08 | Re: Translation updates for zh_CN.po (Chinese Simplified) |
| Previous Message | Alvaro Herrera | 2019-05-28 20:36:55 | Re: PostgreSQL misspellings in translations |