public inbox for [email protected]  

help / color / mirror / Atom feed

From: Guillaume Lelarge <[email protected]>
To: Alvaro Herrera <[email protected]>
Cc: Thomas Munro <[email protected]>
Cc: [email protected]
Subject: Re: Minor backend fr.po mistake
Date: Sat, 30 Nov 2024 15:08:51 +0100
Message-ID: <CAECtzeWjXsd=Ce6=TwE8Rb_20sVTwA0O6+ogM_1NXN8OO6tDdg@mail.gmail.com> (raw)
In-Reply-To: <[email protected]>
References: <CA+hUKGLABQhPCyAezKfUhAPBS7Lkg_E0BBXgdwMHy7cf5afQQw@mail.gmail.com>
	<[email protected]>

Le sam. 30 nov. 2024 à 15:00, Alvaro Herrera <[email protected]> a
écrit :

> 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.
>
>
While I still translate lock in french ("verrou"), I don't translate
trigger anymore. Noone understood what I meant with "déclencheur". And
every DBA, even French ones :) , knows what a trigger is.


> 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.
>
>
I tend to stick with "immutable", as French people understand this term.
Maybe there's still some "immuable", I'll try to fix them.


-- 
Guillaume.

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], [email protected]
  Subject: Re: Minor backend fr.po mistake
  In-Reply-To: <CAECtzeWjXsd=Ce6=TwE8Rb_20sVTwA0O6+ogM_1NXN8OO6tDdg@mail.gmail.com>

* 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