From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Ken Moffat <zarniwhoop@ntlworld.com>, Jonathan Corbet <corbet@lwn.net>
Cc: 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>,
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:46:26 +0700 [thread overview]
Message-ID: <ZUSzYtBpvAmM3ZRs@debian.me> (raw)
In-Reply-To: <ZUQ-K7MXzHZ_oyVK@llamedos.localdomain>
[-- Attachment #1: Type: text/plain, Size: 4075 bytes --]
On Fri, Nov 03, 2023 at 12:26:19AM +0000, Ken Moffat wrote:
> On Thu, Nov 02, 2023 at 10:35:47AM -0600, Jonathan Corbet wrote:
>
> Jon, some slight nit-picking below, after comments on the stated
> problem.
>
> > Bagas Sanjaya <bagasdotme@gmail.com> writes:
> >
> [...]
> > >
> > > 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.
> >
> Bagas,
>
> If loading the web font fails, you will get whichever fallback
> fonts are enabled by fontconfig and whichever fonts you, or your
> distro, have installed. If those fonts are not generally adequate
> you should complain to your distro, or install different fonts in
> ~/.local/share/fotns and perhaps change your fonts.conf entries.
I beg to differ.
That's depending on font-family rule. For example, if I write it as:
```
body {
font-family: "Liberation Sans", Helvetica, Arial, sans-serif;
}
```
browsers will try loading the first three fonts, in order. If a font
isn't available, they will try the next one until they can. Only then
when all other options are exhausted, generic fallback font will kick
in.
And yes, I do copying all fonts from my Windows installation (since
I dual-boot both it and Debian), then configure GNOME to use Segoe UI
as UI font (as it looks nicer to me). I also drop in font substitution
rules in `~/.config/fontconfig/conf.d` since I'm not the fan of
(obviously non-free) Söhne and substitute it with Inter and Source
Code Pro.
>
> > 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.
> >
>
> Jon,
>
> As I understand it the (woff) fonts would be downloaded on request
> by the browser if this went in. So not a bunch of binary font data
> in the kernel, but a download from google (adding to the popularity
> of the font) and yet more font data in the browser cache. I don't
> have any desire to see woff fonts referenced in the docs, just
> nit-picking about the details.
But I wasn't considering people using terminal-only browsers (like
Lynx).
>
> However -
>
> > - The licensing of the fonts is not fully free.
> >
>
> AFAICS, the SIL OFL allows everything except changing the font name.
> If you have the right tools you can apparently fix things like "that
> specific glyph looks ugly" or "you put a latin breve on a cyrillic
> letter" (apparently they should differ) or "You mismapped this
> codepoint to the wrong glyph". What you cannot do, if those changes
> are not accepted by the font designer/maintainer, or if the font is
> no-longer maintained, is fork it and provide it under the same name.
>
> You can fork, but the font name has to be changed (e.g. LinLibertine
> -> Libertinus and then the serif forked to CommonSerif).
>
> Oh, and you cannot sell the fonts by themselves, but you can bundle
> them with a distro or embed them.
> https://www.tldrlegal.com/license/open-font-license-ofl-explained
>
> Question: is that not free enough, or is that site wrong ? If not
> free enough, is there a better licence for fonts ?
Yet Debian distributes OFL fonts in its main archive...
For me, for the fonts, I'd like CC-BY-SA instead.
Thanks.
--
An old man doll... just what I always wanted! - Clara
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2023-11-03 8: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
2023-11-03 0:26 ` Ken Moffat
2023-11-03 8:46 ` Bagas Sanjaya [this message]
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=ZUSzYtBpvAmM3ZRs@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 \
--cc=zarniwhoop@ntlworld.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.