From: Alex Shi <seakeel@gmail.com>
To: Jonathan Corbet <corbet@lwn.net>,
Yanteng Si <siyanteng@loongson.cn>,
alexs@kernel.org
Cc: chenhuacai@kernel.org, jiaxun.yang@flygoat.com,
linux-doc@vger.kernel.org, realpuyuwang@gmail.com,
bobwxc@email.cn, siyanteng01@gmail.com,
huangjianghui@uniontech.com
Subject: Re: [PATCH v3] docs/zh_CN: add core-api workqueue.rst translation
Date: Fri, 14 May 2021 12:53:36 +0800 [thread overview]
Message-ID: <4eb9f549-d734-a5d2-aa2a-e66d009a31e5@gmail.com> (raw)
In-Reply-To: <87o8de61zz.fsf@meer.lwn.net>
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.
Thanks
Alex
>
> Thanks,
>
> jon
>
next prev parent reply other threads:[~2021-05-14 4:53 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 [this message]
2021-05-14 9:09 ` yanteng si
2021-05-14 9:30 ` Alex Shi
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=4eb9f549-d734-a5d2-aa2a-e66d009a31e5@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).