From: Alex Shi <seakeel@gmail.com>
To: yanteng si <siyanteng01@gmail.com>
Cc: Jonathan Corbet <corbet@lwn.net>,
Yanteng Si <siyanteng@loongson.cn>, Alex Shi <alexs@kernel.org>,
Huacai Chen <chenhuacai@kernel.org>,
Jiaxun Yang <jiaxun.yang@flygoat.com>,
linux-doc@vger.kernel.org, Puyu Wang <realpuyuwang@gmail.com>,
Wu XiangCheng <bobwxc@email.cn>,
huangjianghui@uniontech.com
Subject: Re: [PATCH v3] docs/zh_CN: add core-api workqueue.rst translation
Date: Fri, 14 May 2021 17:30:34 +0800 [thread overview]
Message-ID: <c91e7f95-0c48-292c-d353-d2ca4ac62051@gmail.com> (raw)
In-Reply-To: <CAEensMx6HxD5_Gv2Snd+OGOF0MNU4fsuB_z_pCDWyW8z+5SC=Q@mail.gmail.com>
On 2021/5/14 下午5:09, yanteng si wrote:
> Alex Shi <seakeel@gmail.com> 于2021年5月14日周五 下午12:53写道:
>>
>>
>>
>> On 2021/5/14 上午12:18, Jonathan Corbet wrote:
>>>>> This patch translates Documentation/core-api/workqueue.rst into Chinese.
>>>>>
>>>>>
>>>>> Signed-off-by: Yanteng Si <siyanteng@loongson.cn>
>>>>> Reviewed-by: Alex Shi <alexs@kenrel.org>
>>>> I fixed that typo too - it appears to originate from Alex...:)
>>
>> Sorry for the typo.
>>
>>> Actually, I've dropped this back out; it creates vast numbers of
>>> warnings:
>>>
>>>> Documentation/core-api/workqueue:398: ./include/linux/workqueue.h:3: WARNING: Duplicate C declaration, also
>>>> defined at translations/zh_CN/core-api/workqueue:3.
>>> This will be the result of the ".. kernel-doc::" directives at the end,
>>> which create new definitions (within sphinx) for all the symbols pulled
>>> in.
>>>
>>> In the long term, we may want to try to find some sort of fix for this.
>>> But we're really just recreating a bunch of (English-language)
>>> documentation that's already rendered once; I'm not sure it makes any
>>> real sense to do that. So I would suggest that, for now, when you are
>>> translating documents with kernel-doc directives, you should leave those
>>> directives out. Stick in a note directing readers to the original if
>>> they want to see that material...
>>>
>>> Make sense?
>>
>> Yes, it is a reasonable solution for now.
> OK, I will.
> I will remove them and then direct the reader to the original
> document. just like:
>
> .. note:: 抱歉,由于原始文档在此处交叉引用了代码中的注释,而现在并不是翻译这些注释的好时机(将会带来很多编译警告),所以请暂时浏览英文文档,链接在本文档顶部。
Jon said just remove kernel-doc, not all line? If so, don't need above explanation.
>
> Thanks,
> Yanteng
>>
>> Thanks
>> Alex
>>>
>>> Thanks,
>>>
>>> jon
>>>
next prev parent reply other threads:[~2021-05-14 9:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-12 8:33 [PATCH v3] docs/zh_CN: add core-api workqueue.rst translation Yanteng Si
2021-05-13 15:19 ` Jonathan Corbet
2021-05-13 16:18 ` Jonathan Corbet
2021-05-14 4:53 ` Alex Shi
2021-05-14 9:09 ` yanteng si
2021-05-14 9:30 ` Alex Shi [this message]
2021-05-14 9:47 ` yanteng si
2021-05-14 10:40 ` Alex Shi
2021-05-14 14:48 ` yanteng si
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=c91e7f95-0c48-292c-d353-d2ca4ac62051@gmail.com \
--to=seakeel@gmail.com \
--cc=alexs@kernel.org \
--cc=bobwxc@email.cn \
--cc=chenhuacai@kernel.org \
--cc=corbet@lwn.net \
--cc=huangjianghui@uniontech.com \
--cc=jiaxun.yang@flygoat.com \
--cc=linux-doc@vger.kernel.org \
--cc=realpuyuwang@gmail.com \
--cc=siyanteng01@gmail.com \
--cc=siyanteng@loongson.cn \
/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).