| From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
| Cc: | Greg Stark <stark(at)mit(dot)edu>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Robert Haas <robertmhaas(at)gmail(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: WIP patch for consolidating misplaced-aggregate checks |
| Date: | 2012-08-15 03:48:37 |
| Message-ID: | 1345002517.17599.17.camel@vanquo.pezone.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, 2012-08-14 at 11:30 -0400, Alvaro Herrera wrote:
> And so on (there are several more). Note that here we use "check
> constraint" without any capitalization. However this doesn't
> translate
> too well as is; I mean, if I were to translate "check" into its
> equivalent spanish word, I'm sure to cause a great deal of confusion.
> So I've opted for putting the check word, verbatim, in quotes; for
> example:
>
> msgid "check constraint \"%s\" already exists"
> msgstr "la restricción «check» «%s» ya existe"
>
> However this is also a bit ugly because I now have two sets of quoted
> words -- check itself and then the constraint name.
I can't really advise you with the language issue, but I think just
writing check without quotes would be fine here. I also find it useful
on occasion to consult existing (non-PostgreSQL, non-MySQL) books about
databases in the respective language for typical translations.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2012-08-15 03:54:53 | Re: -Wformat-zero-length |
| Previous Message | Peter Eisentraut | 2012-08-15 03:44:53 | Re: WIP patch for consolidating misplaced-aggregate checks |