linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Federico Vaga <federico.vaga@vaga.pv.it>
To: Jonathan Corbet <corbet@lwn.net>
Cc: Alex Shi <alex.shi@linux.alibaba.com>,
	linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] doc: add translation disclaimer
Date: Tue, 19 Mar 2019 09:03:53 +0100	[thread overview]
Message-ID: <14381941.zoZXB8H0OD@pcbe13614> (raw)
In-Reply-To: <20190318113534.43fb94f3@lwn.net>

On Monday, March 18, 2019 6:35:34 PM CET Jonathan Corbet wrote:
> On Thu, 14 Mar 2019 21:45:16 +0100
> 
> Federico Vaga <federico.vaga@vaga.pv.it> wrote:
> > Add the translation disclaimer in English as reference
> > for other languages.  Translations must include this disclaimer
> > in their language so that readers are properly informed.
> > 
> > This very same patch updates the Italian translation accordingly.
> > 
> > Signed-off-by: Federico Vaga <federico.vaga@vaga.pv.it>
> 
> Honestly, it all feels a little too legalistic to me; have people been
> worried about the translations in this regard?
> 
> Oh well, I went ahead and applied it.  I do think that it might make sense
> to move the TOC *above* the disclaimer, though, since that's what readers
> are really going to be interested in.

No, problem I can do it and send a new version

> 
> Thanks,
> 
> jon


-- 
Federico Vaga
http://www.federicovaga.it/



  reply	other threads:[~2019-03-19  8:03 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-14 20:45 [PATCH] doc: add translation disclaimer Federico Vaga
2019-03-15  5:49 ` Alex Shi
2019-03-15  8:09   ` Federico Vaga
2019-03-15 23:00   ` Federico Vaga
2019-03-15 10:00 ` Rasmus Villemoes
2019-03-15 10:55   ` Federico Vaga
2019-03-18 17:35 ` Jonathan Corbet
2019-03-19  8:03   ` Federico Vaga [this message]
2019-03-19 13:35     ` Jonathan Corbet
2019-03-23 17:37       ` 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=14381941.zoZXB8H0OD@pcbe13614 \
    --to=federico.vaga@vaga.pv.it \
    --cc=alex.shi@linux.alibaba.com \
    --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).