Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::3:6 as permitted sender) client-ip=2620:137:e000::3:6;
From:   Jonathan Corbet <corbet@lwn.net>
To:     Hu Haowen <src.res.211@gmail.com>
Cc:     Hu Haowen <src.res.211@gmail.com>, linux-kernel@vger.kernel.org,
        linux-doc@vger.kernel.org
Subject: Re: [PATCH] docs/zh_TW: update contents for zh_TW
In-Reply-To: <20230917084646.92319-1-src.res.211@gmail.com>
References: <20230917084646.92319-1-src.res.211@gmail.com>
Date:   Sat, 23 Sep 2023 02:00:28 -0600
Message-ID: <87r0mp5nfn.fsf@meer.lwn.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Precedence: bulk

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

> The content of zh_TW was too outdated comparing to the original files.
> Consequently carry out improvements in order to both keep track of sources
> and fix several grammatical mistakes in traditional Chinese.
>
> This is a thorough rewrite of the previous patch:
>     https://lore.kernel.org/linux-doc/20230807120006.6361-1-src.res.211@g=
mail.com/
> in order to get rid of text damage and merging errors, created based on
> linux-next (date: Sept. 15, 2023).
>
> Signed-off-by: Hu Haowen <src.res.211@gmail.com>

So I get the usual sort of problem here:

> WARNING: Message contains suspicious unicode control characters!
>          Subject: [PATCH] docs/zh_TW: update contents for zh_TW
>             Line:  =EF=BB=BF.. _tw_process_statement_kernel:
>             -------^
>             Char: ZERO WIDTH NO-BREAK SPACE (0xfeff)
>          If you are sure about this, rerun with the right flag to allow.
> AM FAILED

*Please* try applying your patches before sending them so we can avoid
this sort of difficulty.

jon