From: Federico Vaga <federico.vaga@vaga.pv.it>
To: Alex Shi <alex.shi@linux.alibaba.com>
Cc: linux-doc@vger.kernel.org, lkml <linux-kernel@vger.kernel.org>,
Jonathan Corbet <corbet@lwn.net>,
harryxiyou@gmail.com, Li Zefan <lizefan@huawei.com>,
Shawn Guo <shawn.guo@linaro.org>,
Fengguang Wu <fengguang.wu@intel.com>
Subject: Re: [RFC PATCH] doc: translation disclaimer
Date: Mon, 11 Mar 2019 22:02:01 +0100 [thread overview]
Message-ID: <833e824cd99f7ed282dfe175ae59876d@vaga.pv.it> (raw)
In-Reply-To: <8aad62be-e088-c5e1-e2df-a270c62ce1a1@linux.alibaba.com>
On 2019-03-07 05:03, Alex Shi wrote:
> On 2019/3/6 11:17 下午, Federico Vaga wrote:
>
>> As I wrote in the commit message, this is just a example to show
>> the
>> structure and share the main message.
>>
>> What I wrote is just a 10 minutes sketch, to share an idea. This is
>> **not**
>> the text that I'm proposing; what I'm proposing here are the
>> structure and the
>> concepts/ideas/messages. The final patch will be written
>> appropriately, but
>> before doing it I would like to collect the messages that we want to
>> put in
>> it; I listed above what I think is necessary to say.
>
> Got it. yes, it's a good idea, and we'd better figure out the more
> elegant, precise and legally words. :)
I wouldn't go that far with the legal jargon. There is nothing legal
about
this, only that who read a translation must be aware of its limitations.
>> +
>> +Translations
>> +------------
>> +
>>
>> .. toctree::
>> :maxdepth: 1
>>
>> diff --git a/Documentation/translations/it_IT/disclaimer-ita.rst
>> b/Documentation/translations/it_IT/disclaimer-ita.rst index
>> d68e52de6a5d..aacc1a0346db 100644
>> --- a/Documentation/translations/it_IT/disclaimer-ita.rst
>> +++ b/Documentation/translations/it_IT/disclaimer-ita.rst
>> @@ -1,13 +1,6 @@
>>
>> :orphan:
>>
>> why the orphan here? does that mean no maintainer for it_IT
>> currently?
>
> It is a Sphinx tag to avoid warnings at build time. Instead of
> re-writing
> exactly the same text in all files, this one is included at the top of
> all
> translated documents. But, since it is not a real document this is not
>
> included in any TOC and sphinx complains; that's why we need the
> orphan tag
>
> http://www.sphinx-doc.org/en/master/usage/restructuredtext/field-lists.html#metadata
>
> Thanks a lot for the explanations! :)
--
Federico Vaga
http://www.federicovaga.it/
prev parent reply other threads:[~2019-03-11 21:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-05 22:06 [RFC PATCH] doc: translation disclaimer Federico Vaga
2019-03-06 1:57 ` Alex Shi
2019-03-06 15:17 ` Federico Vaga
[not found] ` <8aad62be-e088-c5e1-e2df-a270c62ce1a1@linux.alibaba.com>
2019-03-11 21:02 ` 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=833e824cd99f7ed282dfe175ae59876d@vaga.pv.it \
--to=federico.vaga@vaga.pv.it \
--cc=alex.shi@linux.alibaba.com \
--cc=corbet@lwn.net \
--cc=fengguang.wu@intel.com \
--cc=harryxiyou@gmail.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lizefan@huawei.com \
--cc=shawn.guo@linaro.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