linux-doc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: Alex Shi <seakeel@gmail.com>, Tang Yizhou <tangyizhou@huawei.com>
Cc: Yanteng Si <siyanteng@loongson.cn>,
	yanteng si <siyanteng01@gmail.com>, Alex Shi <alexs@kernel.org>,
	Linux Doc Mailing List <linux-doc@vger.kernel.org>,
	zhengbin13@huawei.com, Yeechou Tang <tangyeechou@gmail.com>
Subject: Re: [PATCH 1/1] docs/zh_CN: Add sched-capacity translation
Date: Tue, 07 Dec 2021 07:57:40 -0700	[thread overview]
Message-ID: <87ee6o1mzf.fsf@meer.lwn.net> (raw)
In-Reply-To: <CAJy-AmmdGQndsx3MDhYCgqawc-JRib7-YGm1oDit2hW1otbjuQ@mail.gmail.com>

Alex Shi <seakeel@gmail.com> writes:

> What the result of scripts/checkpatch.pl or make htmldocs say?
> Let's tame these tools and follow the regluar styles of kernel.

checkpatch knows nothing about different languages, and "make htmldocs"
doesn't do that sort of stylistic checking.

I don't know enough (i.e. anything :) to have an opinion on the best
length for lines of Chinese text.  Surely there must be some conventions
out there?

Thanks,

jon

  parent reply	other threads:[~2021-12-07 14:57 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-06  9:09 [RFC PATCH 0/1] Add sched-capacity Chinese translation Tang Yizhou
2021-12-06  9:09 ` [PATCH 1/1] docs/zh_CN: Add sched-capacity translation Tang Yizhou
2021-12-07  5:37   ` Alex Shi
2021-12-07  7:46     ` Tang Yizhou
2021-12-07  8:34       ` yanteng si
2021-12-07  9:33         ` Feiyang Chen
2021-12-07  9:57           ` yanteng si
2021-12-07  9:59           ` Alex Shi
2021-12-07 13:30             ` Tang Yizhou
2021-12-07  9:41       ` Alex Shi
2021-12-07 13:18         ` Tang Yizhou
2021-12-07 14:57         ` Jonathan Corbet [this message]
2021-12-08  3:16           ` Alex Shi
2021-12-08  4:35             ` Tang Yizhou
2021-12-08  4:54               ` yanteng si
2021-12-08  6:15                 ` Alex Shi
2021-12-08  7:11                   ` yanteng si
2021-12-08  6:37                 ` Feiyang Chen

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=87ee6o1mzf.fsf@meer.lwn.net \
    --to=corbet@lwn.net \
    --cc=alexs@kernel.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=seakeel@gmail.com \
    --cc=siyanteng01@gmail.com \
    --cc=siyanteng@loongson.cn \
    --cc=tangyeechou@gmail.com \
    --cc=tangyizhou@huawei.com \
    --cc=zhengbin13@huawei.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;
as well as URLs for NNTP newsgroup(s).