From: Yanteng Si <siyanteng@loongson.cn>
To: Gang Li <gang.li@linux.dev>
Cc: Leo Yan <leo.yan@linaro.org>,
Alex Shi <alex.shi@linux.alibaba.com>,
linux-doc@vger.kernel.org, linux-arch@vger.kernel.org,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
Alan Stern <stern@rowland.harvard.edu>,
Andrea Parri <parri.andrea@gmail.com>,
Will Deacon <will@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Boqun Feng <boqun.feng@gmail.com>,
Nicholas Piggin <npiggin@gmail.com>,
David Howells <dhowells@redhat.com>,
Jade Alglave <j.alglave@ucl.ac.uk>,
Luc Maranget <luc.maranget@inria.fr>,
"Paul E. McKenney" <paulmck@kernel.org>,
Akira Yokosawa <akiyks@gmail.com>,
Daniel Lustig <dlustig@nvidia.com>,
Joel Fernandes <joel@joelfernandes.org>,
Jonathan Corbet <corbet@lwn.net>, Alex Shi <alexs@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH v1] docs/zh_CN: add zh_CN translation for memory-barriers.txt
Date: Tue, 22 Aug 2023 20:09:53 +0800 [thread overview]
Message-ID: <bee90784-e53c-4a30-b1f5-feeba46c7f5a@loongson.cn> (raw)
In-Reply-To: <20230821125322.GB57731@leoy-huanghe.lan>
在 2023/8/21 20:53, Leo Yan 写道:
> On Mon, Aug 21, 2023 at 02:39:15PM +0800, Gang Li wrote:
>> Thanks for your review!
>>
>> Your suggestions will be integrated into the next version(v2).
>>
>> On 2023/8/20 00:25, Leo Yan wrote:
>>>> + | | : | | : | |
>>>> + | | : | | : | |
>>>> + | CPU 1 |<----->| 内存 |<----->| CPU 2 |
>>> Unalignment caused by extra space around "内存".
>>>
>> If using Chinese, it is impossible to align properly no matter
>> how it is modified. If strict alignment is needed, the text in the
>> charts should not be translated.
> In my editor (vim), a Chinese character is two-width of English
> character. So you could see in above, I can simply remove a space for
> alignment.
Hi Gang,
Yes, we will use vim to make adjustments in the end, no matter what
editor we use for this work.
BTW, The title should also be aligned, with one Chinese character and
two "=".
Just like:
-+==========
-+免责声明
-+==========
++========
++免责声明
++========
Thanks,
Yanteng
> Anyway, if you have different editor or configuration, using either
> langauge is fine for me.
>
> Please expect I will have more review.
>
> Thanks,
> Leo
next prev parent reply other threads:[~2023-08-22 12:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-11 6:22 Gang Li
2023-08-19 16:25 ` Leo Yan
2023-08-21 6:39 ` Gang Li
2023-08-21 12:53 ` Leo Yan
2023-08-22 12:09 ` Yanteng Si [this message]
2023-08-20 16:50 ` Leo Yan
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=bee90784-e53c-4a30-b1f5-feeba46c7f5a@loongson.cn \
--to=siyanteng@loongson.cn \
--cc=akiyks@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=alex.shi@linux.alibaba.com \
--cc=alexs@kernel.org \
--cc=boqun.feng@gmail.com \
--cc=corbet@lwn.net \
--cc=dhowells@redhat.com \
--cc=dlustig@nvidia.com \
--cc=gang.li@linux.dev \
--cc=j.alglave@ucl.ac.uk \
--cc=joel@joelfernandes.org \
--cc=leo.yan@linaro.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=luc.maranget@inria.fr \
--cc=npiggin@gmail.com \
--cc=parri.andrea@gmail.com \
--cc=paulmck@kernel.org \
--cc=peterz@infradead.org \
--cc=stern@rowland.harvard.edu \
--cc=will@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