| From: | Daniele Varrazzo <daniele(dot)varrazzo(at)gmail(dot)com> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Fixed redundant i18n strings in json |
| Date: | 2014-08-02 13:15:26 |
| Message-ID: | CA+mi_8YMbUMtFsbuPTL8DNauxFraE5ia8==jp6Yqbp8oCn_6Gg@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
I'd definitely replace /arg/argument/. Furthermore I'd avoid the form
"argument 1: something is wrong": the string is likely to end up in
sentences with other colons so I'd rather use "something is wrong at
argument 1".
Is the patch attached better?
Cheers,
-- Daniele
On Thu, Jul 31, 2014 at 1:57 PM, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
> On Wed, Jul 30, 2014 at 2:59 PM, Daniele Varrazzo
> <daniele(dot)varrazzo(at)gmail(dot)com> wrote:
>> Please find attached a small tweak to a couple of strings found while
>> updating translations. The %d version is already used elsewhere in the
>> same file.
>
> Probably not a bad idea, but aren't these strings pretty awful anyway?
> At a minimum, "arg" as an abbreviation for "argument" doesn't seem
> good.
>
> --
> Robert Haas
> EnterpriseDB: http://www.enterprisedb.com
> The Enterprise PostgreSQL Company
| Attachment | Content-Type | Size |
|---|---|---|
| fixarg2.patch | text/x-patch | 2.9 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2014-08-02 15:09:00 | Re: Fwd: Re: Compile fails on AIX 6.1 |
| Previous Message | Peter Geoghegan | 2014-08-02 09:45:41 | Re: B-Tree support function number 3 (strxfrm() optimization) |