From: David Vernet <void@manifault.com>
To: Jonathan Corbet <corbet@lwn.net>
Cc: Bagas Sanjaya <bagasdotme@gmail.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Documentation <linux-doc@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Akira Yokosawa <akiyks@gmail.com>,
Stanislav Fomichev <sdf@google.com>,
Miguel Ojeda <ojeda@kernel.org>, James Seo <james@equiv.tech>,
Daniel Vetter <daniel.vetter@ffwll.ch>,
Federico Vaga <federico.vaga@vaga.pv.it>,
Carlos Bilbao <carlos.bilbao@amd.com>
Subject: Re: [PATCH RFC RESEND 0/4] Documentation: Web fonts for kernel documentation
Date: Thu, 2 Nov 2023 11:45:50 -0500 [thread overview]
Message-ID: <20231102164550.GA3640@maniforge> (raw)
In-Reply-To: <874ji48658.fsf@meer.lwn.net>
On Thu, Nov 02, 2023 at 10:35:47AM -0600, Jonathan Corbet wrote:
> Bagas Sanjaya <bagasdotme@gmail.com> writes:
Hello Bagas,
[...]
> > The solution
> > ============
> >
> > Uniform the font choices by leveraging web fonts. Most of people reading
> > the kernel docs should already have modern browser that supports this
> > feature (e.g. Chrome/Chromium and Firefox). The fonts are downloaded
> > automatically when loading the page, but only if the reader don't
> > already have ones installed locally. Subsequent docs page loading will
> > use the browser cache to retrieve the fonts. If for some reasons the
> > fonts fail to load, the browser will fall back to fallback fonts
> > commonly seen on other sites.
>
> So my immediate response to this is pretty uniformly negative.
>
> - If you don't like serif, tweaking conf.py is easy enough without
> pushing it on everybody else.
>
> - I'm not thrilled about adding a bunch of binary font data to the
> kernel, and suspect a lot of people would not feel that the bloat is
> worth it.
>
> - The licensing of the fonts is not fully free.
+1 to all of Jon's points. We already have to deal with folks arguing
against .rst and pushing for us to just use plaintext for everything. I
suspect their reaction to this would be, to put it politely, even less
restrained.
Thanks,
David
next prev parent reply other threads:[~2023-11-02 16:46 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-02 12:32 [PATCH RFC RESEND 0/4] Documentation: Web fonts for kernel documentation Bagas Sanjaya
2023-11-02 12:32 ` [PATCH RFC RESEND 1/4] LICENSES: Add SIL Open Font License 1.1 Bagas Sanjaya
2023-11-02 14:09 ` Greg Kroah-Hartman
2023-11-03 7:44 ` Bagas Sanjaya
2023-11-02 12:32 ` [PATCH RFC RESEND 2/4] Docmentation: Use IBM Plex Sans for page body Bagas Sanjaya
2023-11-02 16:02 ` Randy Dunlap
2023-11-02 12:32 ` [PATCH RFC RESEND 3/4] Documentation: Use Newsreader font for document headings Bagas Sanjaya
2023-11-02 12:32 ` [PATCH RFC RESEND 4/4] Documentation: Use IBM Plex Mono as monospace font Bagas Sanjaya
2023-11-02 16:35 ` [PATCH RFC RESEND 0/4] Documentation: Web fonts for kernel documentation Jonathan Corbet
2023-11-02 16:45 ` David Vernet [this message]
2023-11-03 0:26 ` Ken Moffat
2023-11-03 8:46 ` Bagas Sanjaya
2023-11-03 8:29 ` 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=20231102164550.GA3640@maniforge \
--to=void@manifault.com \
--cc=akiyks@gmail.com \
--cc=bagasdotme@gmail.com \
--cc=carlos.bilbao@amd.com \
--cc=corbet@lwn.net \
--cc=daniel.vetter@ffwll.ch \
--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=ojeda@kernel.org \
--cc=sdf@google.com \
--cc=tglx@linutronix.de \
/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).