From: Federico Vaga <federico.vaga@vaga.pv.it>
To: Jonathan Corbet <corbet@lwn.net>
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
Alessia Mantegazza <amantegazza@vaga.pv.it>
Subject: Re: doc: Italian translation
Date: Mon, 28 May 2018 15:22:00 +0200 [thread overview]
Message-ID: <4469233.YSvUztRfSp@pcbe13614> (raw)
In-Reply-To: <20180528070828.3a3c7287@lwn.net>
On Monday, 28 May 2018 15:08:28 CEST Jonathan Corbet wrote:
> On Sun, 27 May 2018 16:55:55 +0200
>
> Federico Vaga <federico.vaga@vaga.pv.it> wrote:
> > here the doc-guide translated in Italian. This set of patches
> > includes some minor changes to the main one. The idea of this
> > first set of patches is also to adjust the structure and our
> > expectations.
>
> I've only done a quick scan so far. It looks reasonable, but I have
> a couple of requests:
>
> - Please include a proper changelog with each patch describing what
> the patch does and why. Otherwise I'll have to fill them in, and
> that makes me grumpy...:)
Ok
> - You might as well add a MAINTAINERS entry. The other
> translations don't have them, but they should.
Ok
> - For extra credit: it's time to move the translations out of the
> top-level index into an index.rst in the translations directory.
> Then the top-level file can have a single pointer to the
> translations.
I completely agree on this point. I can prepare a patch that does it.
> > We tried to translate everything in **Italian**; which means that
> > we avoided imported English words wherever there is the
> > possibility to use the Italian ones. Of course, this is not
> > always possible, or worst doing the translation make it less
> > clear, for example the word "file".
>
> "We"? Is there somebody else's work represented here too? If so,
> they should appear in the signoff chain (or as a Co-developed-by
> credit).
I did, in patch 3/5 and 4/5 there is Alessia as "signed-off" (in CC
here).
> > Another point. I noticed that the disclaimer for other
> > translations is in English, so I did the same. But actually
> > shouldn't be in Italian, since that page will be read by Italian
> > speakers?
>
> Perhaps, though part of the idea is to give the English speakers,
> too, some vague clue of what they're looking at.
Make sense. I will keep it like this then.
Thanks
>
> Thanks,
>
> jon
--
Federico Vaga
http://www.federicovaga.it/
--
To unsubscribe from this list: send the line "unsubscribe linux-doc" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2018-05-28 13:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-27 14:55 doc: Italian translation Federico Vaga
2018-05-27 14:55 ` [PATCH 1/5] doc: typos and minor fixes Federico Vaga
2018-05-27 14:55 ` [PATCH 2/5] doc: add chapter labels Federico Vaga
2018-05-27 14:55 ` [PATCH 3/5] doc: add Italian translation skeleton Federico Vaga
2018-05-27 14:55 ` [PATCH 4/5] doc:it_IT: add doc-guide translation Federico Vaga
2018-05-28 13:08 ` doc: Italian translation Jonathan Corbet
2018-05-28 13:22 ` Federico Vaga [this message]
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=4469233.YSvUztRfSp@pcbe13614 \
--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).