From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Documentation <linux-doc@vger.kernel.org>,
Jonathan Corbet <corbet@lwn.net>,
Thomas Gleixner <tglx@linutronix.de>,
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>,
linux-spdx@vger.kernel.org, Richard Fontana <rfontana@redhat.com>
Subject: Re: [PATCH RFC 1/4] LICENSES: Add SIL Open Font License 1.1
Date: Sat, 4 Nov 2023 07:53:07 +0700 [thread overview]
Message-ID: <ZUWV88wRf9suUQfH@debian.me> (raw)
In-Reply-To: <2023110317-unhealthy-playable-d5d6@gregkh>
[-- Attachment #1: Type: text/plain, Size: 3054 bytes --]
On Fri, Nov 03, 2023 at 09:49:54AM +0100, Greg Kroah-Hartman wrote:
> On Fri, Nov 03, 2023 at 03:11:36PM +0700, Bagas Sanjaya wrote:
> > On Thu, Nov 02, 2023 at 03:06:19PM +0100, Greg Kroah-Hartman wrote:
> > > On Thu, Nov 02, 2023 at 07:00:43PM +0700, Bagas Sanjaya wrote:
> > > > LICENSES/dual/OFL-1.1 | 107 ++++++++++++++++++++++++++++++++++++++++++
> > >
> > > You add this license, but then never actually reference it in the later
> > > changes, so it's going to be very confusing as to why it is here. Any
> > > way to add it to the font files themselves so our checker tools can
> > > handle this properly?
> >
> > There is TTF name string ID called "License". For example, on IBM Plex Sans,
> > the string value is:
> >
> > ```
> > This Font Software is licensed under the SIL Open Font License, Version 1.1. This license is available with a FAQ at: http://scripts.sil.org/OFL
> > ```
> >
> > Checking that string requires scripting fontforge, and since the string value
> > may differ (but has the same license) across different fonts, scripting it
> > can be non-trivial.
>
> And is that in the files you added? They are binary so it's hard to
> determine this :(
Yes.
>
> > >
> > > And, it's not going to work as a dual-license, you can't just suddenly
> > > dual-license those font files, right?
> >
> > I was thinking of putting OFL in LICENSES/exceptions instead due to this
> > nature.
>
> Yes, it can not be a dual one.
That's right!
What about just saying below in the CSS file that includes the fonts?
```
...
/* Some cool fonts are licensed under OFL 1.1, see
* LICENSES/exceptions/OFL-1.1 for more information. */
...
```
> > > > +Usage-Guide:
> > > > + Do NOT use this license for code, but it's acceptable for fonts (where the
> > > > + license is specifically written for them). It's best to use it together
> > > > + with a GPL2 compatible license using "OR", as OFL-1.1 texts processed by
> > > > + the kernel's build system might combine it with content taken from more
> > > > + restrictive licenses.
> > > > + To use the SIL Open Font License 1.1, put the following SPDX tag/value pair
> > > > + into a comment according to the placement guidelines in the licensing rules
> > > > + documentation:
> > > > + SPDX-License-Identifier: OFL-1.1
> > >
> > > Where did this Usage-Guide from?
> >
> > Adapted from LICENSES/dual/CC-BY-4.0.
>
> Which it shouldn't be :(
>
> Anyway, this is independent of the issue if we actually should take
> these fonts into the kernel tree, and mandate their use (my opinion is
> no, that's not for us to use, and especially for any action that might
> cause a web browser to look elsewhere outside of our documentation.)
>
> Also, for documentation, I'm pretty sure that serif fonts is proven to
> be "nicer" overall by many studies.
Any pointer to them? Or do serif fonts more readable and not causing
eye strain?
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-04 0:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20231102120053.30630-1-bagasdotme@gmail.com>
2023-11-02 12:00 ` [PATCH RFC 1/4] LICENSES: Add SIL Open Font License 1.1 Bagas Sanjaya
2023-11-02 14:06 ` Greg Kroah-Hartman
2023-11-03 8:11 ` Bagas Sanjaya
2023-11-03 8:49 ` Greg Kroah-Hartman
2023-11-04 0:53 ` Bagas Sanjaya [this message]
2023-11-04 9:52 ` Greg Kroah-Hartman
2023-11-05 23:40 ` Bagas Sanjaya
2023-11-02 14:09 ` Richard Fontana
2023-11-03 8: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=ZUWV88wRf9suUQfH@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=linux-spdx@vger.kernel.org \
--cc=ojeda@kernel.org \
--cc=rfontana@redhat.com \
--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 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 read-only IMAP folder(s) and NNTP newsgroup(s).