From: | Guillaume Lelarge <guillaume(at)lelarge(dot)info> |
---|---|
To: | Thomas Munro <thomas(dot)munro(at)gmail(dot)com> |
Cc: | pgsql-translators(at)postgresql(dot)org |
Subject: | Re: Minor backend fr.po mistake |
Date: | 2024-11-30 13:38:01 |
Message-ID: | CAECtzeV4PwQJF9wSEGMs1-sKU3dBTktDcmtwVdLLpc6ca94wew@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-translators |
Hi,
Le sam. 30 nov. 2024 à 05:15, Thomas Munro <thomas(dot)munro(at)gmail(dot)com> a
écrit :
> Hi,
>
> #, c-format
> msgid "This may be because of a non-immutable index expression."
> msgstr "Ceci peut être dû à une expression d'index immutable."
>
> Should be "NON immutable".
>
>
You're right, my mistake. I've fixed it on all maintained releases.
> (Or non immuable, or is that just muable... Just kidding but I am a
> bit confused about why "immutable" is preserved in English. In this
> case it's referring to observed behaviour of an expression that must
> have been considered immutable by static analysis but seems not to be
> at execution time. In another case we use the French word "immuable"
> (no T) when talking about immutability by static analysis (that is,
> whether all functions are declared IMMUTABLE). Other messages and
> languages made various choices about when to translate, quote or
> uppercase the words immutable and volatile. Wow, this is hard.)
>
>
Immutable and volatile exist in French (though the right word should be
"immuable", but usually French DBAs know what immutable is).
Thanks for your report.
--
Guillaume.
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2024-11-30 14:00:18 | Re: Minor backend fr.po mistake |
Previous Message | Thomas Munro | 2024-11-30 04:14:42 | Minor backend fr.po mistake |