From: Alex Shi <seakeel@gmail.com>
To: Dongliang Mu <mudongliangabcd@gmail.com>
Cc: "Dongliang Mu" <dzm91@hust.edu.cn>,
si.yanteng@linux.dev, "Alex Shi" <alexs@kernel.org>,
"Yanteng Si" <siyanteng@loongson.cn>,
"Jonathan Corbet" <corbet@lwn.net>,
"Miguel Ojeda" <ojeda@kernel.org>,
"Alex Gaynor" <alex.gaynor@gmail.com>,
"Boqun Feng" <boqun.feng@gmail.com>,
"Gary Guo" <gary@garyguo.net>,
"Björn Roy Baron" <bjorn3_gh@protonmail.com>,
"Benno Lossin" <benno.lossin@proton.me>,
"Andreas Hindborg" <a.hindborg@kernel.org>,
"Alice Ryhl" <aliceryhl@google.com>,
"Trevor Gross" <tmgross@umich.edu>,
"Nathan Chancellor" <nathan@kernel.org>,
"Nick Desaulniers" <ndesaulniers@google.com>,
"Bill Wendling" <morbo@google.com>,
"Justin Stitt" <justinstitt@google.com>,
hust-os-kernel-patches@googlegroups.com,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
rust-for-linux@vger.kernel.org, llvm@lists.linux.dev
Subject: Re: [PATCH v3] docs/zh_CN: update the translation of process/programming-language.rst
Date: Thu, 24 Oct 2024 11:02:28 +0800 [thread overview]
Message-ID: <8a8fdd5a-44e6-42b9-a920-ff00ac7dc57d@gmail.com> (raw)
In-Reply-To: <CAD-N9QV-EBbSkrZ5TSUt7j3MhsAHMozY59gFOEnSQ1HB9cUsZg@mail.gmail.com>
On 10/24/24 10:51, Dongliang Mu wrote:
>>>> Hi Dongliang,
>>>>
>>>> Good job! Most of translation are good.
>>>> Just the above doc seems still English version, give them a zh_cn name may cause misunderstand?
>>> Oh, I see. However, you cannot use gcc or rustc since it already exists in the English documents. We need another name to make sphinx happy. Therefore, why do not we directly use the final version of name? :)
>>>
>> Uh, is it possible to use English version 'gcc' links in this doc? Otherwise,it make sense too.
>>
> https://lore.kernel.org/all/bae3c59c-39a5-4daa-b37e-bbf077d57643@hust.edu.cn/T/#m8a948b24401404806f53e086f57856cf3a56a490
>
> v2 patch triggers a warning due to duplicate links. So I crafted a v3
> version to use zh_cn prefix before each link
OK. That's fine for this patch. But for long term view, it's better to find a way for duplicate links.
Reviewed-by: Alex Shi <alexs@kernel.org>
next prev parent reply other threads:[~2024-10-24 3:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-23 6:27 [PATCH v3] docs/zh_CN: update the translation of process/programming-language.rst Dongliang Mu
2024-10-24 2:21 ` Alex Shi
2024-10-24 2:30 ` Dongliang Mu
2024-10-24 2:40 ` Alex Shi
2024-10-24 2:51 ` Dongliang Mu
2024-10-24 3:02 ` Alex Shi [this message]
2024-10-24 3:06 ` Dongliang Mu
2024-10-24 19:34 ` Jonathan Corbet
2024-10-24 20:01 ` Jonathan Corbet
2024-10-24 21:02 ` Jonathan Corbet
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=8a8fdd5a-44e6-42b9-a920-ff00ac7dc57d@gmail.com \
--to=seakeel@gmail.com \
--cc=a.hindborg@kernel.org \
--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=hust-os-kernel-patches@googlegroups.com \
--cc=justinstitt@google.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@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=si.yanteng@linux.dev \
--cc=siyanteng@loongson.cn \
--cc=tmgross@umich.edu \
/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