[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <87r0mp5nfn.fsf@meer.lwn.net>
Date: Sat, 23 Sep 2023 02:00:28 -0600
From: Jonathan Corbet <corbet@....net>
To: Hu Haowen <src.res.211@...il.com>
Cc: Hu Haowen <src.res.211@...il.com>, linux-kernel@...r.kernel.org,
linux-doc@...r.kernel.org
Subject: Re: [PATCH] docs/zh_TW: update contents for zh_TW
Hu Haowen <src.res.211@...il.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@gmail.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@...il.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: .. _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
Powered by blists - more mailing lists