From: Federico Vaga <federico.vaga@vaga.pv.it>
To: Andi Shyti <andi.shyti@kernel.org>
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
workflows@vger.kernel.org, Jonathan Corbet <corbet@lwn.net>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Subject: Re: [PATCH] Doc:it_IT: Do not reference kernel.h anymore
Date: Mon, 15 Dec 2025 00:30:04 +0000 [thread overview]
Message-ID: <zylu4ulxeyni5diwnp7o7evcajqyylhzzd4d2skyi2ul2ayb3b@2kojo3dyp2vi> (raw)
In-Reply-To: <20251205111559.3089219-1-andi.shyti@kernel.org>
Hi Andi,
thank you for contributing to the Italian translation.
On Fri, Dec 05, 2025 at 12:15:58PM +0100, Andi Shyti wrote:
>I also took the chance to improve the phrasing in a few places.
As a technical translation, we should not try to make reinterpretation of the
original text. See comments below.
>Andi
>
> .../it_IT/process/coding-style.rst | 19 +++++++++++--------
> 1 file changed, 11 insertions(+), 8 deletions(-)
>
>diff --git a/Documentation/translations/it_IT/process/coding-style.rst b/Documentation/translations/it_IT/process/coding-style.rst
>index c0dc786b8474..b2fd74528de5 100644
>--- a/Documentation/translations/it_IT/process/coding-style.rst
>+++ b/Documentation/translations/it_IT/process/coding-style.rst
>@@ -1068,15 +1068,17 @@ può migliorare la leggibilità.
> 18) Non reinventate le macro del kernel
> ---------------------------------------
>
>-Il file di intestazione include/linux/kernel.h contiene un certo numero
>-di macro che dovreste usare piuttosto che implementarne una qualche variante.
>-Per esempio, se dovete calcolare la lunghezza di un vettore, sfruttate la
>-macro:
>+I file header
In Italian, the correct name for "header file" is "file di intestazione".
Please, don't replace correct Italian with *Itanglese* :)
>presenti in include/linux mettono a disposizione numerose macro
>+che è preferibile utilizzare, evitando di sviluppare implementazioni
>+alternative.
I think it is less accurate. In English, it tells users what they "should do"
and "should not do". It does not speak about what is preferable and what to
avoid. I agree that, at the end of the day, one should come at the same
conclusions. However, the translation should be as accurate as possible and
make adaptations wherever necessary to improve the understanding.
A would be perfectly fine if also the English statement changes in the same
direction.
Including your suggestions I would write:
"""
I file di intestazione presenti in include/linux mettono a disposizione numerose
macro che dovreste utilizzare piuttosto che implementarne delle varianti.
"""
>@@ -1084,10 +1086,11 @@ struttura, usate
>
> #define sizeof_field(t, f) (sizeof(((t*)0)->f))
>
>-Ci sono anche le macro min() e max() che, se vi serve, effettuano un controllo
>-rigido sui tipi. Sentitevi liberi di leggere attentamente questo file
>-d'intestazione per scoprire cos'altro è stato definito che non dovreste
>-reinventare nel vostro codice.
>+definita in stddef.h.
>+
>+Ci sono anche le macro min() e max() definite in minmax.h che effettuano un
>+controllo rigoroso sui tipi.
Here it is loosing the "if you need them". If removed here, it should be removed
also in the English version. Of course, one use functions if they are needed, it
comes without saying.
>È consigliato consultare i vari file header per
>+vedere altre macro già disponibili.
"file header" -> "file di intestazione"
Here, the English text is more colloquial and speaks to users with some irony.
In your adaptation these things are lost. Which is fine if also the English version
looses it with a more cold/professional "It is recommanded reading ...".
--
Federico Vaga
next prev parent reply other threads:[~2025-12-15 0:30 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-26 21:46 [PATCH v2 1/1] docs: Update documentation to avoid mentioning of kernel.h Andy Shevchenko
2025-11-27 0:26 ` Randy Dunlap
2025-11-29 15:24 ` Andy Shevchenko
2025-11-29 15:54 ` Jonathan Corbet
2025-11-29 17:46 ` Andy Shevchenko
2025-11-27 17:34 ` Joe Perches
2025-11-27 18:19 ` Andy Shevchenko
2025-12-05 11:15 ` [PATCH] Doc:it_IT: Do not reference kernel.h anymore Andi Shyti
2025-12-15 0:30 ` Federico Vaga [this message]
2025-12-15 16:14 ` Andi Shyti
2025-12-17 22:48 ` Federico Vaga
2025-12-22 22:01 ` Jonathan Corbet
2025-12-23 21:22 ` Federico Vaga
2025-12-23 21:34 ` Jonathan Corbet
2025-12-05 15:25 ` [PATCH v2 1/1] docs: Update documentation to avoid mentioning of kernel.h Mathieu Poirier
2025-12-22 22:00 ` Jonathan Corbet
2025-12-28 18:02 ` Andy Shevchenko
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=zylu4ulxeyni5diwnp7o7evcajqyylhzzd4d2skyi2ul2ayb3b@2kojo3dyp2vi \
--to=federico.vaga@vaga.pv.it \
--cc=andi.shyti@kernel.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=workflows@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox