public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
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
Date: Sat, 23 Sep 2023 02:00:28 -0600	[thread overview]
Message-ID: <87r0mp5nfn.fsf@meer.lwn.net> (raw)
In-Reply-To: <20230917084646.92319-1-src.res.211@gmail.com>

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@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@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:  .. _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

      reply	other threads:[~2023-09-23  8:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-17  8:46 [PATCH] docs/zh_TW: update contents for zh_TW Hu Haowen
2023-09-23  8:00 ` Jonathan Corbet [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87r0mp5nfn.fsf@meer.lwn.net \
    --to=corbet@lwn.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=src.res.211@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox