From: Andi Shyti <andi.shyti@kernel.org>
To: Federico Vaga <federico.vaga@vaga.pv.it>
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 17:14:02 +0100 [thread overview]
Message-ID: <klzag46p6mlqqdrogqofancqyjpvs5lmwa4m3tjszcgavdwa6s@nay2uuwpsvlt> (raw)
In-Reply-To: <zylu4ulxeyni5diwnp7o7evcajqyylhzzd4d2skyi2ul2ayb3b@2kojo3dyp2vi>
Hi Federico,
> >-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* :)
I absolutely disagree.
If you open any C book, they are called 'header files', except
for a few Italian technical books with excessively literal
translations, where even non-translatable terms are translated.
Italian technical translations usually preserve the original
English terms as much as possible, which is quite different from
what often happens in French or German.
'File di intestazione' is a literal word-by-word translation.
If you want the proper technical term, it is 'header file'.
> >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.
I think a literal translation is not beneficial to the final
text, and we have some room to rephrase it while keeping the
original meaning intact.
Andi
next prev parent reply other threads:[~2025-12-15 16:14 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
2025-12-15 16:14 ` Andi Shyti [this message]
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=klzag46p6mlqqdrogqofancqyjpvs5lmwa4m3tjszcgavdwa6s@nay2uuwpsvlt \
--to=andi.shyti@kernel.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=corbet@lwn.net \
--cc=federico.vaga@vaga.pv.it \
--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