From: "Wu X.C." <bobwxc@email.cn>
To: Jiabing Wan <wanjiabing@vivo.com>
Cc: teng sterling <sterlingteng@gmail.com>,
Alex Shi <alexs@kernel.org>, Jonathan Corbet <corbet@lwn.net>,
Paul Walmsley <paul.walmsley@sifive.com>,
Palmer Dabbelt <palmer@dabbelt.com>,
Albert Ou <aou@eecs.berkeley.edu>,
Nathan Chancellor <nathan@kernel.org>,
Nick Desaulniers <ndesaulniers@google.com>,
Bernard Zhao <bernard@vivo.com>,
Fangrui Song <maskray@google.com>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-riscv@lists.infradead.org,
clang-built-linux@googlegroups.com
Subject: Re: Re: [PATCH] docs/zh_CN: add translations in zh_CN/dev-tools/kasan
Date: Wed, 2 Jun 2021 16:06:18 +0800 [thread overview]
Message-ID: <20210602080618.GA13557@bobwxc.top> (raw)
In-Reply-To: <AJsAIwDhDrLmLTPKOHKvbark.3.1622615414473.Hmail.wanjiabing@vivo.com>
[-- Attachment #1: Type: text/plain, Size: 712 bytes --]
On Wed, Jun 02, 2021 at 02:30:14PM +0800, Jiabing Wan wrote:
>
> >> +
> >> +软件 KASAN 模式(#1 和 #2)使用编译时工具在每次内存访问之前插入有效性检查,
> >Delete the spaces before and after KASAN, these spaces don't look good
> >inside the html.
>
> I'll fix them,thank you.
> BTW, how about other English words, like "SLUB", "free"?
> It seems most english word in this document are surround with spaces...
>
Now we don't add spaces between Chinese and English.
It is easy to add spaces, but hard to remove someday ;)
I think the "space" should be resolved by format control like CSS or
xeCJK (yes, latex's xeCJK will control such space).
Thanks,
Wu X.C.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]
prev parent reply other threads:[~2021-06-02 8:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-01 8:38 Wan Jiabing
2021-06-01 13:11 ` teng sterling
2021-06-02 6:30 ` Jiabing Wan
2021-06-02 8:06 ` Wu X.C. [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=20210602080618.GA13557@bobwxc.top \
--to=bobwxc@email.cn \
--cc=alexs@kernel.org \
--cc=aou@eecs.berkeley.edu \
--cc=bernard@vivo.com \
--cc=clang-built-linux@googlegroups.com \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=maskray@google.com \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=sterlingteng@gmail.com \
--cc=wanjiabing@vivo.com \
/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
all inboxes | Powered by JetHome®