linux-kernel - Re: [PATCH RESEND v1] docs/zh_CN: add zh_CN translation for memory-barriers.txt

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <5c3829b0-1844-23b9-c708-88095d510954@linux.dev>
Date:   Thu, 17 Aug 2023 11:03:59 +0800
From:   Gang Li <gang.li@...ux.dev>
To:     Yanteng Si <siyanteng@...ngson.cn>,
        Patrick Yingxi Pan <pyxchina92929@...il.com>
Cc:     seakeel@...il.com, Alex Shi <alexs@...nel.org>,
        linux-doc@...r.kernel.org, linux-arch@...r.kernel.org,
        linux-mm@...ck.org, linux-kernel@...r.kernel.org,
        Alan Stern <stern@...land.harvard.edu>,
        Andrea Parri <parri.andrea@...il.com>,
        Will Deacon <will@...nel.org>,
        Peter Zijlstra <peterz@...radead.org>,
        Boqun Feng <boqun.feng@...il.com>,
        Nicholas Piggin <npiggin@...il.com>,
        David Howells <dhowells@...hat.com>,
        Jade Alglave <j.alglave@....ac.uk>,
        Luc Maranget <luc.maranget@...ia.fr>,
        "Paul E. McKenney" <paulmck@...nel.org>,
        Akira Yokosawa <akiyks@...il.com>,
        Daniel Lustig <dlustig@...dia.com>,
        Joel Fernandes <joel@...lfernandes.org>,
        Jonathan Corbet <corbet@....net>,
        Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: [PATCH RESEND v1] docs/zh_CN: add zh_CN translation for
 memory-barriers.txt

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.