public inbox for [email protected]  

help / color / mirror / Atom feed

From: Alvaro Herrera <[email protected]>
To: Thomas Munro <[email protected]>
Cc: [email protected]
Subject: Re: Minor backend fr.po mistake
Date: Sat, 30 Nov 2024 15:00:18 +0100
Message-ID: <[email protected]> (raw)
In-Reply-To: <CA+hUKGLABQhPCyAezKfUhAPBS7Lkg_E0BBXgdwMHy7cf5afQQw@mail.gmail.com>

On 2024-Nov-30, Thomas Munro wrote:

> #, 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".

Agreed.

> (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.)

Yeah, it is hard.  Sometimes we keep the English term because for the
user it's clearer exactly which property is meant.  For instance, in the
Spanish translation I used to translate "locks" as "candados" and
"triggers" as "disparadores", but per user feedback I ended reverting
that into using the English words in quotes.  Examples:

msgid "permission denied for event trigger %s"
msgstr "permiso denegado al “trigger” por eventos %s"

msgid "could not obtain lock on relation \"%s.%s\""
msgstr "no se pudo bloquear un “lock” en la relación «%s.%s»"

(This is quite new and has not yet propagated to 17, but it will by the
February release).  I think users understand this better.


Anyway I see that the French translation tends to use "immutable"
everywhere rather than "immuable".  It might be just a typo, or somebody
was not consistent.

-- 
Álvaro Herrera               48°01'N 7°57'E  —  https://www.EnterpriseDB.com/

view thread (6+ messages)  latest in thread

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected]
  Subject: Re: Minor backend fr.po mistake
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox