linux-doc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Randy Dunlap <rdunlap@infradead.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Documentation <linux-doc@vger.kernel.org>
Cc: Jonathan Corbet <corbet@lwn.net>,
	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: Sun, 22 Jun 2025 14:19:35 +0700	[thread overview]
Message-ID: <aFeuh_HOH8d2rXL6@archie.me> (raw)
In-Reply-To: <1067bbff-be53-4bec-9cec-8a4d0f531fb7@infradead.org>

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

On Thu, Jun 19, 2025 at 12:12:38AM -0700, Randy Dunlap wrote:
> Hi Bagas,
> 
> On 6/18/25 9:23 PM, Bagas Sanjaya wrote:
> > The reason why serif fonts is used for headings in complement to sans
> > serif in text body is to break up visual monotony of docs page by
> > creating contrast between headings (as entry point to docs information)
> > and text body, which is important considering that kernel docs are
> > quite lengthy with many sections.
> 
> It's interesting that mediawiki chose to split the serif and sans serif
> usage this way. Newspapers essentially do the opposite: use sans serif
> for headlines (mostly, not consistently) and use serif for body text.

IMO I found that sans-serif is more pleasant to eye (i.e. lesser strain)
than Times New Roman on screen. My htmldocs build now uses Google Sans
Display and Roboto Mono, though (as web fonts).

> 
> 
> Have you read "The Psychology of Computer Programming"?
> [https://geraldmweinberg.com/Site/Programming_Psychology.html]
> The content is very good but (at least in early editions) it was printed
> completely using a sans serif font (probably Helvetica). It's not a
> long book and I found the subject very interesting, but it took me
> forever to read it because it's (or was, don't know about the later
> editions) in sans serif typeface. I hated that part of it.

I didn't read it, unfortunately, due to financial constraints.
(Oh, and in Indonesia where I live people usually shop things online
at Shopee, Tokopedia, and Lazada [my go-to marketplace] instead
of Amazon.)

> 
> So I applied this patch and tested it. It works as far as I can tell.
> I got tons of sans serif font text instead of serif font text that I
> don't care for. (I don't mind that the sidebar text is sans serif.)

I keep the headings on sidebar in sans-serif. Also, the body text is
darkened (but not completely black) to give contrast between docs
body and sidebar.

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-22  7:19 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-19  4:23 [PATCH RFC] Documentation: typography refresh Bagas Sanjaya
2025-06-19  7:12 ` Randy Dunlap
2025-06-22  7:19   ` Bagas Sanjaya [this message]
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

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=aFeuh_HOH8d2rXL6@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=rdunlap@infradead.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;
as well as URLs for NNTP newsgroup(s).