From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Carlos Bilbao <carlos.bilbao.osdev@gmail.com>,
Vegard Nossum <vegard.nossum@oracle.com>,
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: Wed, 25 Jun 2025 07:35:41 +0700 [thread overview]
Message-ID: <fb2d7547-dd6e-4f6a-978f-b92ae2eb20cb@gmail.com> (raw)
In-Reply-To: <250eb150-ef18-4e62-9791-f2ec4801cd39@gmail.com>
On 6/25/25 05:59, Carlos Bilbao wrote:
> I'll be honest -- I was initially skeptical about the value of changing
> fonts. But I do see how the updated typography improves readability and
> feels friendlier overall. It follows modern web design trends like
> Wikipedia’s; but I do wonder if we’re trading off some of the "personality"
> of rough/challenging aura that fits kernel dev. Your new version feels a
> bit less hacky/unique. Anyway, font preferences are subjective, e.g., I've
> seen people run terminals with white backgrounds!
>
I'm also leaning towards following web trends by this font tweak, though.
And yeah, when I first coded my HTML and CSS code in school, my peers
would've like to use non-monospace fonts ({sans-}serif) in Windows
Notepad without knowing that it was bad idea (as they didn't know that
monospace was the norm).
> What I’m more concerned about is that if we merge this, someone else might
> want to tweak another part of the UX next week simply because it “looks
> better” to them. We've to draw a line on what kind of UX changes we’re open
> to. From my side:
>
> Nacked-by: Carlos Bilbao <carlos.bilbao@kernel.org>
>
> Still, I really appreciate the effort you put into this, and I agree that
> readability matters, especially for long docs like ours.
>
Any suggestions without this tweak?
Thanks.
--
An old man doll... just what I always wanted! - Clara
next prev parent reply other threads:[~2025-06-25 0:35 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 [this message]
[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=fb2d7547-dd6e-4f6a-978f-b92ae2eb20cb@gmail.com \
--to=bagasdotme@gmail.com \
--cc=akiyks@gmail.com \
--cc=alexs@kernel.org \
--cc=avadhut.naik@amd.com \
--cc=carlos.bilbao.osdev@gmail.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=vegard.nossum@oracle.com \
--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®