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: Thomas Gleixner <tglx@linutronix.de>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Akira Yokosawa <akiyks@gmail.com>,
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>,
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: Fri, 3 Nov 2023 15:29:32 +0700 [thread overview]
Message-ID: <ZUSvbCVCC25vMyNH@debian.me> (raw)
In-Reply-To: <874ji48658.fsf@meer.lwn.net>
[-- Attachment #1: Type: text/plain, Size: 1707 bytes --]
On Thu, Nov 02, 2023 at 10:35:47AM -0600, Jonathan Corbet wrote:
> 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.
As local commit of course.
>
> - 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.
MediaWiki project takes the same stance regarding web fonts:
> What about using webfonts?
>
> Webfonts is a system to deliver a font to users who do not have it installed.
> This involves having a user's browser download a font we provide, which causes
> additional resources to load and would have a negative impact on site
> performance (i.e. how fast pages load). This is particularly true for older
> browsers. In the future we may explore using webfonts, but for now this update
> provides greater readability and consistency while not degrading page load
> times.
Indeed, it's possible to achieve the same effect without resorting to web
fonts (as MediaWiki did), see [1].
>
> - The licensing of the fonts is not fully free.
That was being discussed on the original RFC thread.
>
> There's so much we can do to improve our documentation and access to it;
> messing around with web fonts seems - to me, at least - pretty low on
> the list.
>
> I suppose I can ask people at the kernel summit session in a couple
> weeks to see if others feel differently.
OK, I want to hear about their opinion.
Thanks.
[1]: https://www.mediawiki.org/wiki/Typography_refresh
--
An old man doll... just what I always wanted! - Clara
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
prev parent reply other threads:[~2023-11-03 8:29 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
2023-11-03 0:26 ` Ken Moffat
2023-11-03 8:46 ` Bagas Sanjaya
2023-11-03 8:29 ` 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=ZUSvbCVCC25vMyNH@debian.me \
--to=bagasdotme@gmail.com \
--cc=akiyks@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 \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.