From: Yanteng Si <siyanteng@loongson.cn>
To: Dongliang Mu <mudongliangabcd@gmail.com>
Cc: ojeda@kernel.org, corbet@lwn.net, alex.gaynor@gmail.com,
wedsonaf@gmail.com, boqun.feng@gmail.com, gary@garyguo.net,
bjorn3_gh@protonmail.com, benno.lossin@proton.me,
a.hindborg@samsung.com, aliceryhl@google.com, nathan@kernel.org,
ndesaulniers@google.com, morbo@google.com,
justinstitt@google.com, alexs@kernel.org, dzm91@hust.edu.cn,
linux-doc@vger.kernel.org, rust-for-linux@vger.kernel.org,
llvm@lists.linux.dev
Subject: Re: [PATCH v1 2/4] docs/zh_CN/rust: Update the translation of coding-guidelines to 6.9-rc4
Date: Fri, 26 Apr 2024 14:21:32 +0800 [thread overview]
Message-ID: <e19151b2-641b-4a0a-a88e-de4d879fbd8a@loongson.cn> (raw)
In-Reply-To: <CAD-N9QXbToYg4VUDmStJ5Nt3Wu4o9UrNCaDQPMcq9tLrd=bdXA@mail.gmail.com>
在 2024/4/23 22:25, Dongliang Mu 写道:
> On Tue, Apr 23, 2024 at 10:09 PM Dongliang Mu <mudongliangabcd@gmail.com> wrote:
>> On Tue, Apr 23, 2024 at 9:08 PM Yanteng Si <siyanteng@loongson.cn> wrote:
>>> Update to commit bc2e7d5c298a ("rust: support `srctree`-relative links")
>>>
>>> Signed-off-by: Yanteng Si <siyanteng@loongson.cn>
>>> ---
>>> .../translations/zh_CN/rust/coding-guidelines.rst | 12 ++++++++++++
>>> 1 file changed, 12 insertions(+)
>>>
>>> diff --git a/Documentation/translations/zh_CN/rust/coding-guidelines.rst b/Documentation/translations/zh_CN/rust/coding-guidelines.rst
>>> index 6c0bdbbc5a2a..d02e2dbff509 100644
>>> --- a/Documentation/translations/zh_CN/rust/coding-guidelines.rst
>>> +++ b/Documentation/translations/zh_CN/rust/coding-guidelines.rst
>>> @@ -157,6 +157,18 @@ https://commonmark.org/help/
>>>
>>> https://doc.rust-lang.org/rustdoc/how-to-write-documentation.html
>>>
>>> +此外，内核支持通过在链接目标前缀 ``srctree/`` 来创建相对于源代码树的链接。例如:
>> 前缀通常被用作名词。建议可以改成：
>>
>> 此外，内核支持通过在链接目标前添加 ``srctree/`` 来创建相对于源代码树的链接。例如:
>
> Translate the above comments to English:
>
> “前缀” in Chinese usually means noun other than verb. So I suggest the
> liberal translation "在...前添加" other than "前缀".
Okay!
Thanks,
Yanteng
>
>
> 2.31.4
>
>
next prev parent reply other threads:[~2024-04-26 6:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-23 13:07 [PATCH v1 0/4] rust: docs: Update the translation of rust to 6.9-rc4 Yanteng Si
2024-04-23 13:07 ` [PATCH v1 1/4] docs/zh_CN/rust: Update the translation of arch-support " Yanteng Si
2024-04-25 9:01 ` Miguel Ojeda
2024-04-25 11:38 ` Yanteng Si
2024-04-23 13:07 ` [PATCH v1 2/4] docs/zh_CN/rust: Update the translation of coding-guidelines " Yanteng Si
2024-04-23 14:09 ` Dongliang Mu
2024-04-23 14:25 ` Dongliang Mu
2024-04-26 6:21 ` Yanteng Si [this message]
2024-04-23 13:09 ` [PATCH v1 3/4] docs/zh_CN/rust: Update the translation of general-information " Yanteng Si
2024-04-23 13:09 ` [PATCH v1 4/4] docs/zh_CN/rust: Update the translation of quick-start " 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=e19151b2-641b-4a0a-a88e-de4d879fbd8a@loongson.cn \
--to=siyanteng@loongson.cn \
--cc=a.hindborg@samsung.com \
--cc=alex.gaynor@gmail.com \
--cc=alexs@kernel.org \
--cc=aliceryhl@google.com \
--cc=benno.lossin@proton.me \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun.feng@gmail.com \
--cc=corbet@lwn.net \
--cc=dzm91@hust.edu.cn \
--cc=gary@garyguo.net \
--cc=justinstitt@google.com \
--cc=linux-doc@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=morbo@google.com \
--cc=mudongliangabcd@gmail.com \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=ojeda@kernel.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=wedsonaf@gmail.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).