Message-ID: <997b4919-ea13-b5a7-0b4e-8c39b63bde0b@redhat.com>
Date:   Mon, 1 Nov 2021 14:59:54 +0100
From:   David Hildenbrand <david@...hat.com>
To:     teng sterling <sterlingteng@...il.com>,
        Alex Shi <seakeel@...il.com>
Cc:     Jonathan Corbet <corbet@....net>,
        Mauro Carvalho Chehab <mchehab+huawei@...nel.org>,
        Linux Doc Mailing List <linux-doc@...r.kernel.org>,
        Alex Shi <alexs@...nel.org>,
        Andrew Morton <akpm@...ux-foundation.org>,
        Wu XiangCheng <bobwxc@...il.cn>,
        Yanteng Si <siyanteng@...ngson.cn>,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH v3 16/23] docs: translations: zh_CN: memory-hotplug.rst:
 fix a typo

On 01.11.21 14:38, teng sterling wrote:
> Alex Shi <seakeel@...il.com> 于2021年11月1日周一 下午3:48写道：
>>
>> On Wed, Oct 20, 2021 at 3:08 PM David Hildenbrand <david@...hat.com> 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

Powered by blists - more mailing lists