linux-kernel - Re: [PATCH v5 1/2] docs: add traditional Chinese translation for kernel Documentation

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: <871r7mw34y.fsf@meer.lwn.net>
Date:   Sun, 25 Jul 2021 14:27:09 -0600
From:   Jonathan Corbet <corbet@....net>
To:     Hu Haowen <src.res@...il.cn>
Cc:     panyunwang849@...il.com, linux-doc@...r.kernel.org,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH v5 1/2] docs: add traditional Chinese translation for
 kernel Documentation

Hu Haowen <src.res@...il.cn> writes:

> 在 2021/7/25 下午10:17, Jonathan Corbet 写道:
>> Hu Haowen <src.res@...il.cn> writes:
>>
>>> Add traditional Chinese translation (zh_TW) for the Linux Kernel
>>> documentation with a series of translated files.
>>>
>>> Signed-off-by: Hu Haowen <src.res@...il.cn>
>>> Reviewed-by: Pan Yunwang <panyunwang849@...il.com>
>> When you send a new version of a patch set, please include (after the
>> "---" line) what changed.  Otherwise maintainers have no idea why you
>> keep sending the patch out or whether it seems to be stabilizing.
>
>
> Sorry, forgot to append them.
>
> v2:
> * Added more translations for zh_TW.
>
> v3:
> * Fixed building errors.
> * Added SPDX identifiers for each file.
>
> v4:
> * Reorganised patch format and compressed patch content.
>
> v5:
> * Added Reviewed-by tag.

OK, I tried to apply these, but it adds a new warning:

  Documentation/translations/zh_TW/process/embargoed-hardware-issues.rst:25: WARNING: duplicate label zh_contact, other instance in Documentation/translations/zh_CN/process/embargoed-hardware-issues.rst

Please get to a point where you don't add any warnings, and I guess
we're good to go.  I do hope there's a reader community for all of this
work, and that it will be kept current...

Thanks,

jon