public inbox for [email protected]help / color / mirror / Atom feed
Minor backend fr.po mistake 6+ messages / 4 participants [nested] [flat]
* Minor backend fr.po mistake @ 2024-11-30 04:14 Thomas Munro <[email protected]> 0 siblings, 2 replies; 6+ messages in thread From: Thomas Munro @ 2024-11-30 04:14 UTC (permalink / raw) To: pgsql-translators 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". (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.) ^ permalink raw reply [nested|flat] 6+ messages in thread
* Re: Minor backend fr.po mistake @ 2024-11-30 13:38 Guillaume Lelarge <[email protected]> parent: Thomas Munro <[email protected]> 1 sibling, 0 replies; 6+ messages in thread From: Guillaume Lelarge @ 2024-11-30 13:38 UTC (permalink / raw) To: Thomas Munro <[email protected]>; +Cc: pgsql-translators Hi, Le sam. 30 nov. 2024 à 05:15, Thomas Munro <[email protected]> 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. ^ permalink raw reply [nested|flat] 6+ messages in thread
* Re: Minor backend fr.po mistake @ 2024-11-30 14:00 Alvaro Herrera <[email protected]> parent: Thomas Munro <[email protected]> 1 sibling, 1 reply; 6+ messages in thread From: Alvaro Herrera @ 2024-11-30 14:00 UTC (permalink / raw) To: Thomas Munro <[email protected]>; +Cc: pgsql-translators 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/ ^ permalink raw reply [nested|flat] 6+ messages in thread
* Re: Minor backend fr.po mistake @ 2024-11-30 14:08 Guillaume Lelarge <[email protected]> parent: Alvaro Herrera <[email protected]> 0 siblings, 1 reply; 6+ messages in thread From: Guillaume Lelarge @ 2024-11-30 14:08 UTC (permalink / raw) To: Alvaro Herrera <[email protected]>; +Cc: Thomas Munro <[email protected]>; pgsql-translators 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. ^ permalink raw reply [nested|flat] 6+ messages in thread
* Re: Minor backend fr.po mistake @ 2024-12-01 01:24 Thomas Munro <[email protected]> parent: Guillaume Lelarge <[email protected]> 0 siblings, 1 reply; 6+ messages in thread From: Thomas Munro @ 2024-12-01 01:24 UTC (permalink / raw) To: Guillaume Lelarge <[email protected]>; +Cc: Alvaro Herrera <[email protected]>; pgsql-translators On Sun, Dec 1, 2024 at 3:09 AM Guillaume Lelarge <[email protected]> wrote: > Noone understood what I meant with "déclencheur". And every DBA, even French ones :) , knows what a trigger is. Right, they had to type CREATE TRIGGER to get there. For the names of database objects and other things in the syntax of the language that you have to use to talk to the computer, it makes sense that some translators decide that it should talk back to you in the same way. It's murkier for the more descriptive stuff like mutability. (I wonder what would happen if the message required you decide if the foreign word used as an adjective is variable, but by coincidence you can't tell in any of the current messages, the only ones that come close used a different formulation "marked/marquées/marcadas IMMUTABLE" :-)) Anyway, thanks for the discussion! ^ permalink raw reply [nested|flat] 6+ messages in thread
* Re: Minor backend fr.po mistake @ 2024-12-04 17:53 Peter Eisentraut <[email protected]> parent: Thomas Munro <[email protected]> 0 siblings, 0 replies; 6+ messages in thread From: Peter Eisentraut @ 2024-12-04 17:53 UTC (permalink / raw) To: Thomas Munro <[email protected]>; Guillaume Lelarge <[email protected]>; +Cc: Alvaro Herrera <[email protected]>; pgsql-translators On 01.12.24 02:24, Thomas Munro wrote: > On Sun, Dec 1, 2024 at 3:09 AM Guillaume Lelarge <[email protected]> wrote: >> Noone understood what I meant with "déclencheur". And every DBA, even French ones :) , knows what a trigger is. > > Right, they had to type CREATE TRIGGER to get there. For the names of > database objects and other things in the syntax of the language that > you have to use to talk to the computer, it makes sense that some > translators decide that it should talk back to you in the same way. > It's murkier for the more descriptive stuff like mutability. (I > wonder what would happen if the message required you decide if the > foreign word used as an adjective is variable, but by coincidence you > can't tell in any of the current messages, the only ones that come > close used a different formulation "marked/marquées/marcadas > IMMUTABLE" :-)) I find the Microsoft Terminology Search a good resource for translations of technical terms: https://learn.microsoft.com/en-us/globalization/reference/microsoft-terminology ^ permalink raw reply [nested|flat] 6+ messages in thread
end of thread, other threads:[~2024-12-04 17:53 UTC | newest] Thread overview: 6+ messages (download: mbox mbox.gz follow: Atom feed) -- links below jump to the message on this page -- 2024-11-30 04:14 Minor backend fr.po mistake Thomas Munro <[email protected]> 2024-11-30 13:38 ` Guillaume Lelarge <[email protected]> 2024-11-30 14:00 ` Alvaro Herrera <[email protected]> 2024-11-30 14:08 ` Guillaume Lelarge <[email protected]> 2024-12-01 01:24 ` Thomas Munro <[email protected]> 2024-12-04 17:53 ` Peter Eisentraut <[email protected]>
This inbox is served by agora; see mirroring instructions for how to clone and mirror all data and code used for this inbox