From: Jonathan Corbet <corbet@lwn.net>
To: Jui-Tse Huang <juitse.huang@gmail.com>,
peterz@infradead.org, valentin.schneider@arm.com,
daniel.m.jordan@oracle.com, siyanteng01@gmail.com,
song.bao.hua@hisilicon.com, henrybear327@gmail.com,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: jserv@ccns.ncku.edu.tw, Jui-Tse Huang <juitse.huang@gmail.com>
Subject: Re: [PATCH 1/1] Rewrite mathematical expressions
Date: Wed, 09 Mar 2022 08:38:55 -0700 [thread overview]
Message-ID: <87r17b9lv4.fsf@meer.lwn.net> (raw)
In-Reply-To: <20220309122206.37497-1-juitse.huang@gmail.com>
Jui-Tse Huang <juitse.huang@gmail.com> writes:
> There are lots of mathematical expressions in the documentation
> which are written in plain text format, which costs reader more time to
> recognize the expressions. If those expressions are written in LaTeX
> format which is supported as an extension of Sphinx, the expressions
> might become prettier as well as more straight forward to reader.
I'm sorry, but I'm not going to be able to apply this. We have to think
about the readability of the plain-text documentation *first*, and LeTeX
source scores poorly on that metric.
So, just for example:
> - capacity(cpu) = work_per_hz(cpu) * max_freq(cpu)
> +.. math::
> + \text{capacity(cpu)} = \text{work\_per\_hz(cpu)} \times \text{max\_freq(cpu)}
The document is not improved by this kind of change, even if the
rendered version is prettier.
I do appreciate your effort to make the documentation better, but please
focus on the readability of the original docs and not just the rendered
version.
Thanks,
jon
prev parent reply other threads:[~2022-03-09 15:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-09 12:22 Jui-Tse Huang
2022-03-09 15:38 ` 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=87r17b9lv4.fsf@meer.lwn.net \
--to=corbet@lwn.net \
--cc=daniel.m.jordan@oracle.com \
--cc=henrybear327@gmail.com \
--cc=jserv@ccns.ncku.edu.tw \
--cc=juitse.huang@gmail.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=siyanteng01@gmail.com \
--cc=song.bao.hua@hisilicon.com \
--cc=valentin.schneider@arm.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
all inboxes | Powered by JetHome®