From: Akira Yokosawa <akiyks@gmail.com>
To: Jonathan Corbet <corbet@lwn.net>, linux-doc@vger.kernel.org
Cc: Mauro Carvalho Chehab <mchehab@kernel.org>,
"Maciej W. Rozycki" <macro@orcam.me.uk>,
Miguel Ojeda <ojeda@kernel.org>,
linux-kernel@vger.kernel.org, Akira Yokosawa <akiyks@gmail.com>
Subject: [PATCH 0/5] docs/doc-guide: Sphinx related updates
Date: Thu, 9 Jun 2022 22:21:44 +0900 [thread overview]
Message-ID: <dccb5233-7f4f-1be6-d1f4-bbe9f42f88e0@gmail.com> (raw)
Hi all,
This small set of patches fill in a couple of missing info and update
outdated guidelines in doc-guide/sphinx.rst.
Patch 1/5 adds a footnote on expected improvements of images embedded in
PDF documents by the support of Inkscape in kfigure.py added in v5.18.
Patch 2/5 mentions the make variable SPHINXDIRS, which is helpful in
test-building a subset of documents. This change was inspired by
an earlier comment of Maciej. He also suggested the update of
changes.rst to indicate the requirement of Sphinx 2.4 or later for
"make htmldocs", but changes.rst is not touched in this patch set
as there is an on-going discussion about updating minimal required
version of Sphinx [1].
[1]: "Sphinx pre v3 -- removing support"
https://lore.kernel.org/linux-doc/LO3P123MB26810D190462B6BBBF1305F6C2A19@LO3P123MB2681.GBRP123.PROD.OUTLOOK.COM/
Patches 3/5 and 4/5 are RFCs.
The guidelines for title adornments were written well before the
transition to subdirectory based documentation.
Here, I'm suggesting a version of guidelines based on my personal
preference. I am expecting at least a few comments from others
because I don't think there is any consensus on how far these
guidelines should be followed, especially for existing documents.
This update was inspired by private communication with Miguel and
Jon.
Patch 3/5 updates the guidelines for title adornments. The change is
done in-place for ease of review.
Patch 4/5 moves the item expanded by Patch 3/5 from the bullet lists
into its own subsection.
Patch 5/5 is a PoC of adding a meta title to kernel-doc.rst by using
the "title" directive mentioned in Patch 3/5.
Any feedback is welcome!
Thanks, Akira
--
Akira Yokosawa (5):
docs/doc-guide: Add footnote on Inkscape for better images in PDF
documents
docs/doc-guide: Mention make variable SPHINXDIRS
docs/doc-guide: Update guidelines for title adornments
docs/doc-guide: Pull guidelines for title adornments out into
subsection
docs/doc-guide: Put meta title for kernel-doc HTML page
Documentation/doc-guide/kernel-doc.rst | 2 +
Documentation/doc-guide/sphinx.rst | 98 +++++++++++++++++++-------
2 files changed, 76 insertions(+), 24 deletions(-)
base-commit: f2906aa863381afb0015a9eb7fefad885d4e5a56
--
2.25.1
next reply other threads:[~2022-06-09 13:21 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-09 13:21 Akira Yokosawa [this message]
2022-06-09 13:23 ` [PATCH 1/5] docs/doc-guide: Add footnote on Inkscape for better images in PDF documents Akira Yokosawa
2022-06-09 13:24 ` [PATCH 2/5] docs/doc-guide: Mention make variable SPHINXDIRS Akira Yokosawa
2022-06-09 15:26 ` Jonathan Corbet
2022-06-10 1:58 ` Akira Yokosawa
2022-06-09 13:26 ` [RFC PATCH 3/5] docs/doc-guide: Update guidelines for title adornments Akira Yokosawa
2022-06-10 9:11 ` Jani Nikula
2022-06-10 16:08 ` Miguel Ojeda
2022-06-11 3:15 ` Akira Yokosawa
2022-06-11 23:25 ` Mauro Carvalho Chehab
2022-06-09 13:27 ` [RFC PATCH 4/5] docs/doc-guide: Pull guidelines for title adornments out into subsection Akira Yokosawa
2022-06-09 13:28 ` [PATCH 5/5] docs/doc-guide: Put meta title for kernel-doc HTML page Akira Yokosawa
2022-06-10 16:50 ` [PATCH 0/5] docs/doc-guide: Sphinx related updates Miguel Ojeda
2022-06-24 19:59 ` Jonathan Corbet
2022-06-24 21:48 ` Akira Yokosawa
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=dccb5233-7f4f-1be6-d1f4-bbe9f42f88e0@gmail.com \
--to=akiyks@gmail.com \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=macro@orcam.me.uk \
--cc=mchehab@kernel.org \
--cc=ojeda@kernel.org \
/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).