[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <97c18b17-047d-4ec9-8698-8d4afffbc27b@loongson.cn>
Date: Mon, 14 Aug 2023 21:14:39 +0800
From: Yanteng Si <siyanteng@...ngson.cn>
To: Jonathan Corbet <corbet@....net>, Gang Li <gang.li@...ux.dev>
Cc: Alex Shi <alexs@...nel.org>, Akira Yokosawa <akiyks@...il.com>,
Peter Zijlstra <peterz@...radead.org>,
linux-doc@...r.kernel.org, linux-arch@...r.kernel.org,
linux-mm@...ck.org, linux-kernel@...r.kernel.org,
Alan Stern <stern@...land.harvard.edu>,
Andrea Parri <parri.andrea@...il.com>,
Will Deacon <will@...nel.org>,
Boqun Feng <boqun.feng@...il.com>,
Nicholas Piggin <npiggin@...il.com>,
David Howells <dhowells@...hat.com>,
Jade Alglave <j.alglave@....ac.uk>,
Luc Maranget <luc.maranget@...ia.fr>,
"Paul E. McKenney" <paulmck@...nel.org>,
Daniel Lustig <dlustig@...dia.com>,
Joel Fernandes <joel@...lfernandes.org>,
Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: [PATCH RESEND v1] docs/zh_CN: add zh_CN translation for
memory-barriers.txt
在 2023/8/14 20:50, Jonathan Corbet 写道:
> Yanteng Si <siyanteng@...ngson.cn> writes:
>
>> 在 2023/8/14 10:40, Gang Li 写道:
>>> Hi,
>>>
>>> On 2023/8/12 19:00, Yanteng Si wrote:
>>>> 在 2023/8/11 16:08, Gang Li 写道:
>>>>> +译注:
>>>>> +本文仅为方便汉语阅读,不保证与英文版本同步;
>>>>> +若有疑问,请阅读英文版本;
>>>>> +若有翻译问题,请通知译者;
>>>>> +若想修改文档,也请先修改英文版本。
>>>> In fact, we already have an easier way to do this, just include
>>>> disclaimer-zh_CN.
>>>>
>>>> If you observe the files under .../zh_CN/, they all have a similar
>>>> header, and we can completely follow them.
>>>>
>>> Thanks. I just noticed that there are txt files under
>>> "zh_CN/arch/arm64/" and "zh_CN/video4linux/". They have the same
>>> header, and I will
>>> refer to them in v2.
>>>
>>>> But you should also have noticed that memory-barriers are not a
>>>> standard rst file and will not be built, which will result in it only
>>>> staying in the development tree.
>>>> It won't appear at:
>>> https://docs.kernel.org
>>> https://www.kernel.org/doc/html/latest/
>>>
>>> But people can still access the txt document in this way:
>>> https://www.kernel.org/doc/Documentation/memory-barriers.txt
>>>
>>>> Finally, this patch is too huge and we may need some time to review it.
>>>>
>>> Of course. Would it be more convenient if I split the file into multiple
>>> patches and send them as one series?
>> You didn't have to.
>>
>>
>> If you want to send a series, you can refactor the original document
>> into rst format and make it the first patch of the series.
>>
>> Just like:
>>
>> [PATCH v2 0/2] docs: Refactor memory-barriers.txt and translate it into
>> Chinese
>>
>> [PATCH v2 1/2] docs: convert memory-barriers.txt to RST
> For $REASONS, memory-barriers.txt is staying as .txt, thus, as Gang Li
> pointed out, the wrapper page that pulls it in. The proper solution is
> to create a wrapper for the translated .txt file as well.
Okay.
Hi Gang,
As Jon said, you need to create a wrapper for the translated
memory-barriers.txt.
Thanks,
Yanteng
Powered by blists - more mailing lists