From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id B8F1FC433FE for ; Mon, 1 Nov 2021 14:00:12 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id A0FE261051 for ; Mon, 1 Nov 2021 14:00:12 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S232093AbhKAOCp (ORCPT ); Mon, 1 Nov 2021 10:02:45 -0400 Received: from us-smtp-delivery-124.mimecast.com ([170.10.133.124]:35550 "EHLO us-smtp-delivery-124.mimecast.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231906AbhKAOCn (ORCPT ); Mon, 1 Nov 2021 10:02:43 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1635775209; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=CGF/tc1tys7W0SSlzlHBg4COK2uDj55D54FnN5zXvwg=; b=F6d5wok9IZifOCzZzaPB02i7IZGCYlIWXDyRgTGXkD/p3BTrDosznTFqJ9U2gQIebeShY5 fbS/Q3AAZ9l0Vmz+Is6ph93jyfpFU0Z5IjawnFZktOlc3cbddg0yK5IXdGg6/56bejf4gV RjYtx+36pLx6VLoPdK7e/KQD+F7axm0= Received: from mail-wm1-f71.google.com (mail-wm1-f71.google.com [209.85.128.71]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-34-5i2z6zvTOZSadiwE5MTWrg-1; Mon, 01 Nov 2021 10:00:08 -0400 X-MC-Unique: 5i2z6zvTOZSadiwE5MTWrg-1 Received: by mail-wm1-f71.google.com with SMTP id l4-20020a05600c1d0400b00332f47a0fa3so1013wms.8 for ; Mon, 01 Nov 2021 07:00:08 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:message-id:date:mime-version:user-agent :content-language:to:cc:references:from:organization:subject :in-reply-to:content-transfer-encoding; bh=CGF/tc1tys7W0SSlzlHBg4COK2uDj55D54FnN5zXvwg=; b=Xax9gkLYSVf22pOtWtXfZhnOs6nntejo9alYc0khV8Pd/dEfKjTsIoIeeOs4697WdS ba3kKMDtJJq7tFi4fEzaE+u3V/d6VkT2+7OnvLo66Lw1JsNlvwrrsPJ3piQuaixQu/qO AhRjooVaxxWxyItON71wzSqGszaJSNt5SEQdL3Ito3fo99Vg8ssgMLmsESe/6PKsEWzB x0vd2/GwGBI/D4/A7nUFkt1zxoWM3W1tz2pWVUM2kgPpLAAno4GINM7jcC6C5CEonQ6e x9VJBOhC/QVB+y29BDUmUXRRagwmiUl5vmdG7k4eTMu5ZZTLR3GXrxNwLkJVLQK2LeXj yXlg== X-Gm-Message-State: AOAM532Y1YKsO+W1sY3WaqHYUmWV/s5arkZXFZRkigpRZkGFNns8wiYY qFQAElLi6yFlZjN6jCbc1P+NH3kT6QBqaCWcQMzuFBOO0paf89nz1SfPF1o3q5fp/7VoEfTYj2f y+MvAzorWxPczPBjq0KJ92or9 X-Received: by 2002:adf:a28f:: with SMTP id s15mr37249497wra.138.1635775207113; Mon, 01 Nov 2021 07:00:07 -0700 (PDT) X-Google-Smtp-Source: ABdhPJwAldUsQPP7Lli9jGRoJzxybz2sntHyUvrjKSbHwlWI9s0xBLd2KiypkKB5/K89Pzn79yikWw== X-Received: by 2002:adf:a28f:: with SMTP id s15mr37249383wra.138.1635775206204; Mon, 01 Nov 2021 07:00:06 -0700 (PDT) Received: from [192.168.3.132] (p5b0c692a.dip0.t-ipconnect.de. [91.12.105.42]) by smtp.gmail.com with ESMTPSA id h18sm8369717wre.46.2021.11.01.06.59.55 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 01 Nov 2021 06:59:58 -0700 (PDT) Message-ID: <997b4919-ea13-b5a7-0b4e-8c39b63bde0b@redhat.com> Date: Mon, 1 Nov 2021 14:59:54 +0100 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.2.0 Content-Language: en-US To: teng sterling , Alex Shi Cc: Jonathan Corbet , Mauro Carvalho Chehab , Linux Doc Mailing List , Alex Shi , Andrew Morton , Wu XiangCheng , Yanteng Si , linux-kernel@vger.kernel.org References: <878ryosocf.fsf@meer.lwn.net> From: David Hildenbrand Organization: Red Hat Subject: Re: [PATCH v3 16/23] docs: translations: zh_CN: memory-hotplug.rst: fix a typo In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 01.11.21 14:38, teng sterling wrote: > Alex Shi 于2021年11月1日周一 下午3:48写道： >> >> On Wed, Oct 20, 2021 at 3:08 PM David Hildenbrand wrote: >>> >>> Dumb question that probably has been asked a couple of times already: >>> why do we even maintain a translated doc in-tree? >>> >>> Every time I do an update on the original doc, I for sure can only guess >>> which translated parts need updating. And I really can only update when > Dear David > > Thank you very much for your contribution, in fact, we are always updating the > translations and improving the speed of the sync, so If you are not > good at Chinese > and want to get the sync faster, please CC us when you send the patch. > It would be great if we would get this suggestion automatically, e.g., via get_maintainers.pl --- maybe that's already done, I didn't check. Personally, I don't speak/read any Chinese, so I'm mostly lost staring at the Chinese translation. :) >>> "deleting", not when rewording/adding. So we'll be left with stale doc >>> that will have to be updated manually by $whoever. >> >> cc to the translation maintainers and translator would be helpful? > Alex,Maybe we should provide a translation guide in English, e.g:: > > Dear developers, if you have trouble updating the Chinese documentation after > updating the original documentation, please CC the translator of > that documentation > and the maintainer of the Chinese documentation, and the relevant > documentation > will be updated soon. > >> >>> I don't feel very >>> confident about this. No translated doc is better than outdated >>> translated doc. >> >> Uh, I don't know other languages, but in Chinese, 15 years before >> translated books are still selling well in China. :) >> https://item.jd.com/1075130482.html -> Linux device driver >> https://item.jd.com/10100237.html -> Understanding linux kernel > Yes, I just bought a LDD3 last week.! >_< Yes, these books in particular are still of a lot of value, although outdated. :) The difference is that when you translate a book, there is a date/version attached, meaning, the original book was for example based on kernel v2.XXX. Once you translate the book, it's simply based on the same kernel version. The in-tree doc is similar. You can access the v5.14 doc for example easily via https://www.kernel.org/doc/html/v5.14/. And the Chinese version via https://www.kernel.org/doc/html/v5.14/translations/zh_CN/. If I as a developer perform a doc update in v5.14, and the translation isn't updated until the end of the same release, the versioned documentation will be out of sync. And that happens automatically with a new release. With an out-of-tree translation, there wouldn't really be an issue. Once everything was translated (brought up-to-date), you would mark it has "fully translated doc of v5.15" manually and release it. But maybe the translation maintainers already take proper care of updating any translation just before the new kernel is released. So just my comment after stumbling over in-tree doc translations. -- Thanks, David / dhildenb