From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
Cc: | Pg Hackers <pgsql-hackers(at)postgresql(dot)org>, pgsql-translators(at)postgresql(dot)org |
Subject: | Re: [HACKERS] translatable string fixes |
Date: | 2017-05-24 18:13:52 |
Message-ID: | 2712.1495649632@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-translators |
Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> writes:
> It took me a very long time to figure out how to translate these 9.6-new
> strings in the AM validate routines:
> msgid "gin operator family \"%s\" contains support procedure %s with cross-type registration"
> ...
> Maybe we can use this phrasing:
> "gin operator family %s contains support procedure %s registered with different left and right types"
OK with me, or maybe better "support procedure %s with different left and
right input types". I doubt "registered" adds much.
> The other complaint I have about this one and also other amvalidate
> functions is the hardcoded AM name, so it's actually one string per AM,
> which is annoying (a total of twenty-something messages which are
> actually only four or five different ones). Ignoring the second part of
> the phrase now, we could use this:
> "operator family %s of access method %s contains support procedure %s with cross-type registration"
If that seems better to the actual translators, it's OK with me. It's
not real clear where is the boundary between combining near-duplicate
messages and assembling messages at runtime.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Paul Ramsey | 2017-05-24 18:14:56 | Re: generate_series regression 9.6->10 |
Previous Message | Tom Lane | 2017-05-24 17:28:11 | Re: generate_series regression 9.6->10 |
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2017-05-24 19:51:07 | Re: [HACKERS] pg_upgrade translation |
Previous Message | Daniele Varrazzo | 2017-05-24 13:26:42 | Re: [HACKERS] translatable string fixes |