From: Gang Li <gang.li@linux.dev>
To: Yanteng Si <siyanteng@loongson.cn>,
Patrick Yingxi Pan <pyxchina92929@gmail.com>
Cc: seakeel@gmail.com, Alex Shi <alexs@kernel.org>,
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>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH RESEND v1] docs/zh_CN: add zh_CN translation for memory-barriers.txt
Date: Thu, 17 Aug 2023 11:03:59 +0800 [thread overview]
Message-ID: <5c3829b0-1844-23b9-c708-88095d510954@linux.dev> (raw)
In-Reply-To: <24cf55ad-e40c-4d7c-9007-2906b26d74c2@loongson.cn>
On 2023/8/16 11:06, Yanteng Si wrote:
>
> 在 2023/8/15 19:08, Patrick Yingxi Pan 写道:
>> I haven't read over the entire text yet, but I've found a couple of
>> places
>> where it goes __slightly__ beyond naive translation. The added paragraphs
>> seem to be supplementary remarks which I believe will help understanding
>> to some degree. But will they make future maintenance harder by breaking
>> the one-to-one correspondence between the two versions? After all the
>> original version is perfectly understandable without the remarks.
>
> Yes, this can cause some maintenance headaches, but we can label it in a
> suitable way:
>
> .. note::
>
> 译者xxx, bulabulabula.......
>
> (eg: vim Documentation/translations/zh_CN/core-api/cachetlb.rst
> +189)
>
>
> Or simply in this way:
>
> (译者注: bulabulabula.......)
>
Good advice.
>>
>> In some other places, the translation lost some information which can
>> (and should) be fixed easily.
>
> You're right! translations with missing information are not accepted by
> readers.
>
> faithfulness > expressiveness > elegance 信 > 达 > 雅
>
Since both of you agree to preserve the original meaning in English as
much as possible, and I'm not strongly insisting on "elegance" either,
we can eliminate this overly modified translation method in v2.
prev parent reply other threads:[~2023-08-17 3:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-11 8:08 [PATCH RESEND v1] docs/zh_CN: add zh_CN translation for memory-barriers.txt Gang Li
[not found] ` <2f519a69-8f12-4c07-bf20-6776a5ada256@loongson.cn>
2023-08-14 2:40 ` Gang Li
2023-08-14 7:58 ` Yanteng Si
2023-08-14 10:57 ` Gang Li
2023-08-14 12:50 ` Jonathan Corbet
2023-08-14 13:14 ` Yanteng Si
2023-08-14 14:31 ` Gang Li
[not found] ` <CANJ3EgExk-TC=qx0Dn7wA-RfTE-h3E_E+i1MctvhvV-VEUJFnQ@mail.gmail.com>
2023-08-15 6:37 ` Gang Li
[not found] ` <CANJ3EgGNQhGdppzYWxLOoJ9kqdCVxOOCi89-6qq638fyqnm2fA@mail.gmail.com>
[not found] ` <24cf55ad-e40c-4d7c-9007-2906b26d74c2@loongson.cn>
2023-08-17 3:03 ` Gang Li [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=5c3829b0-1844-23b9-c708-88095d510954@linux.dev \
--to=gang.li@linux.dev \
--cc=akiyks@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=alexs@kernel.org \
--cc=boqun.feng@gmail.com \
--cc=corbet@lwn.net \
--cc=dhowells@redhat.com \
--cc=dlustig@nvidia.com \
--cc=j.alglave@ucl.ac.uk \
--cc=joel@joelfernandes.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=pyxchina92929@gmail.com \
--cc=seakeel@gmail.com \
--cc=siyanteng@loongson.cn \
--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;
as well as URLs for NNTP newsgroup(s).