From: Federico Vaga <federico.vaga@vaga.pv.it>
To: Jonathan Corbet <corbet@lwn.net>
Cc: Alessia Mantegazza <amantegazza@vaga.pv.it>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH V2] doc:it_IT: add some process/* translations
Date: Wed, 10 Oct 2018 19:01:29 +0200 [thread overview]
Message-ID: <36650122.oeEFLVpePO@harkonnen> (raw)
In-Reply-To: <20181007084210.0cec373a@lwn.net>
On Sunday, October 7, 2018 4:42:10 PM CEST Jonathan Corbet wrote:
> Just FYI, I'll hold this until after the start of the merge window.
Ok
> This is starting to be quite a bit of translated material! Are you sure
> you're up to maintaining it all as the documents evolve?
Short answer:
yes
Long answer:
I cannot guarantee that as soon as there are changes in English we are there
to translate them immediately within the same release. We do our best to do
it, but I think that a delay has to be taken into account (a change has to be
accepted first, and then we can translate. Already in the optimal process
there is a delay).
The intention is to continue our translations with "stable" documents so that
maintenance become easier.
As we discussed a bit some time ago, Documentation is not always in sync with
the code, and translations may not be in sync with the official Documentation.
So, I understand your question (fear) and I answer "yes with a human delay"
because we are not a company but just free contributors (which means: we are
using our free time).
next prev parent reply other threads:[~2018-10-10 17:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20181005185157.27819-1-federico.vaga@vaga.pv.it>
2018-10-07 14:42 ` [PATCH V2] doc:it_IT: add some process/* translations Jonathan Corbet
2018-10-10 17:01 ` Federico Vaga [this message]
2018-11-07 22:22 ` Jonathan Corbet
2018-11-08 22:49 ` Federico Vaga
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=36650122.oeEFLVpePO@harkonnen \
--to=federico.vaga@vaga.pv.it \
--cc=amantegazza@vaga.pv.it \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@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;
as well as URLs for NNTP newsgroup(s).