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] [thread-next>] [day] [month] [year] [list]
Message-ID: <87bkg5dp6x.fsf@meer.lwn.net>
Date:   Fri, 21 Jul 2023 13:44:54 -0600
From:   Jonathan Corbet <corbet@....net>
To:     Hu Haowen <src.res.211@...il.com>
Cc:     Hu Haowen <src.res.211@...il.com>,
        linux-doc-tw-discuss@...ts.sourceforge.net,
        linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH RESEND 0/6] docs/zh_TW: update zh_TW's documentation
 from an ascensive aspect

Hu Haowen <src.res.211@...il.com> writes:

> Update zh_TW's documentation concentrating on the following aspects:
>
>     * The file tree structure changes of the main documentation;
>     * Some changes and ideas from zh_CN translation;
>     * Removal for several obsoleted contents within the zh_TW translation
>       or those which are not exising anymore in the main documentation.
>     * Replacements for some incorrect words and phrases in traditional
>       Chinese or those which are odd within their context being hard for
>       readers to comprehend.
>
> Hu Haowen (6):
>   docs/zh_TW: update admin-guide
>   docs/zh_TW: update arch
>   docs/zh_TW: update cpu-freq
>   docs/zh_TW: update filesystems
>   docs/zh_TW: update process
>   docs/zh_TW: turn zh_CN's folder references and headers into zh_TW's
>     ones

So b4 doesn't like this one:

> WARNING: Message contains suspicious unicode control characters!
>          Subject: [PATCH RESEND 5/6] docs/zh_TW: update process
>             Line: +.. SPDX-License-Identifier: GPL-2.0
>             -------^
>             Char: ZERO WIDTH NO-BREAK SPACE (0xfeff)
>          If you are sure about this, rerun with the right flag to allow.
> AM FAILED
> 

Could you resend, please, without the funky control characters?

Thanks,

jon

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ