mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Jonathan Corbet <corbet@lwn.net>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Documentation <linux-doc@vger.kernel.org>
Cc: Mauro Carvalho Chehab <mchehab@kernel.org>,
	Federico Vaga <federico.vaga@vaga.pv.it>,
	Akira Yokosawa <akiyks@gmail.com>,
	Carlos Bilbao <carlos.bilbao@kernel.org>,
	Avadhut Naik <avadhut.naik@amd.com>, Alex Shi <alexs@kernel.org>,
	Yanteng Si <si.yanteng@linux.dev>,
	Dongliang Mu <dzm91@hust.edu.cn>,
	Thomas Gleixner <tglx@linutronix.de>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Stanislav Fomichev <sdf@google.com>,
	David Vernet <void@manifault.com>,
	Miguel Ojeda <ojeda@kernel.org>, James Seo <james@equiv.tech>,
	Daniel Vetter <daniel.vetter@ffwll.ch>
Subject: Re: [PATCH RFC] Documentation: typography refresh
Date: Fri, 27 Jun 2025 07:20:01 +0700	[thread overview]
Message-ID: <aF3jsR6d2gC_CvoE@archie.me> (raw)
In-Reply-To: <87wm8z8xs7.fsf@trenco.lwn.net>

[-- Attachment #1: Type: text/plain, Size: 1707 bytes --]

On Wed, Jun 25, 2025 at 12:46:16PM -0600, Jonathan Corbet wrote:
> Bagas Sanjaya <bagasdotme@gmail.com> writes:
> 
> > At present, kernel documentation uses system serif font for body text.
> > Some people, however, objected to it and instead prefer that the
> > typography choice must be legible, consistent, and accessible (after
> > all, the audience ranges developers peeking into kernel internals to
> > ordinary users that skimmed through Documentation/admin-guide/).
> 
> So I have not seen the objections from "some people"; can you point to
> them, please?

None really but I feel that sans-serif looks aesthetically more pleasant
(to my eyes) on screen than bare Times New Roman.

> 
> > To tackle the problem, follow Wikimedia's typography refresh [1].
> > For the font choices, instead of using web fonts as in previous
> > attempt [2], use:
> >
> >   * Linux Libertine, Georgia, Times for serif (used in h1 and h2
> >     headings)
> >   * system font for sans-serif and monospace
> >
> > This allows for more readability and consistency without sacrificing
> > page load times and bandwidth, as the font choices is most likely
> > already available on many platforms.
> 
> I am open to style changes to make the docs more readable, but I am far
> from convinced that this is it.  Mixing font styles in that way will not
> be universally popular, the claim of "more readability" is
> unsubstantiated, and "consistency" seems out of place when you're making
> the fonts deliberately inconsistent...?

Because I don't have anything else to say in my mind as ideas when writing
this RFC.

Thanks.

-- 
An old man doll... just what I always wanted! - Clara

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

      reply	other threads:[~2025-06-27  0:20 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-19  4:23 Bagas Sanjaya
2025-06-19  7:12 ` Randy Dunlap
2025-06-22  7:19   ` Bagas Sanjaya
2025-06-22  8:58 ` Vegard Nossum
2025-06-23  3:41   ` Bagas Sanjaya
2025-06-24 22:59     ` Carlos Bilbao
2025-06-25  0:35       ` Bagas Sanjaya
     [not found]         ` <CAOc0haLSQVO9RexsMDRJ9zx=TPOi5yC6ADX4VLSbFvi1bhP_iw@mail.gmail.com>
2025-07-03 23:50           ` Jonathan Corbet
2025-07-06 16:14             ` Carlos Bilbao
2025-06-22 12:13 ` Mauro Carvalho Chehab
2025-06-25 18:46 ` Jonathan Corbet
2025-06-27  0:20   ` Bagas Sanjaya [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=aF3jsR6d2gC_CvoE@archie.me \
    --to=bagasdotme@gmail.com \
    --cc=akiyks@gmail.com \
    --cc=alexs@kernel.org \
    --cc=avadhut.naik@amd.com \
    --cc=carlos.bilbao@kernel.org \
    --cc=corbet@lwn.net \
    --cc=daniel.vetter@ffwll.ch \
    --cc=dzm91@hust.edu.cn \
    --cc=federico.vaga@vaga.pv.it \
    --cc=gregkh@linuxfoundation.org \
    --cc=james@equiv.tech \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mchehab@kernel.org \
    --cc=ojeda@kernel.org \
    --cc=sdf@google.com \
    --cc=si.yanteng@linux.dev \
    --cc=tglx@linutronix.de \
    --cc=void@manifault.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®