lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <aF3jsR6d2gC_CvoE@archie.me>
Date: Fri, 27 Jun 2025 07:20:01 +0700
From: Bagas Sanjaya <bagasdotme@...il.com>
To: Jonathan Corbet <corbet@....net>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Linux Documentation <linux-doc@...r.kernel.org>
Cc: Mauro Carvalho Chehab <mchehab@...nel.org>,
	Federico Vaga <federico.vaga@...a.pv.it>,
	Akira Yokosawa <akiyks@...il.com>,
	Carlos Bilbao <carlos.bilbao@...nel.org>,
	Avadhut Naik <avadhut.naik@....com>, Alex Shi <alexs@...nel.org>,
	Yanteng Si <si.yanteng@...ux.dev>, Dongliang Mu <dzm91@...t.edu.cn>,
	Thomas Gleixner <tglx@...utronix.de>,
	Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
	Stanislav Fomichev <sdf@...gle.com>,
	David Vernet <void@...ifault.com>, Miguel Ojeda <ojeda@...nel.org>,
	James Seo <james@...iv.tech>,
	Daniel Vetter <daniel.vetter@...ll.ch>
Subject: Re: [PATCH RFC] Documentation: typography refresh

On Wed, Jun 25, 2025 at 12:46:16PM -0600, Jonathan Corbet wrote:
> Bagas Sanjaya <bagasdotme@...il.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

Download attachment "signature.asc" of type "application/pgp-signature" (229 bytes)

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ