All of lore.kernel.org
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@infradead.org>
To: Akira Yokosawa <akiyks@gmail.com>, Jonathan Corbet <corbet@lwn.net>
Cc: linux-doc@vger.kernel.org, "Иван Иванович" <relect@bk.ru>
Subject: Re: [PATCH] docs: Detect variable fonts and suggest removing them
Date: Sat, 23 Mar 2024 17:34:44 -0700	[thread overview]
Message-ID: <d91ec85c-6a44-4b4a-bfe4-b8ad8fa95c01@infradead.org> (raw)
In-Reply-To: <8361afd6-ac80-4d56-9620-961a7a16cfa7@gmail.com>


>>> ---
>>> Cc: linux-doc@vger.kernel.org
>>> ---
>>>  Documentation/Makefile          |  2 +-
>>>  MAINTAINERS                     |  1 +
>>>  scripts/check-variable-fonts.sh | 30 ++++++++++++++++++++++++++++++
>>>  3 files changed, 32 insertions(+), 1 deletion(-)
>>>  create mode 100755 scripts/check-variable-fonts.sh
>>>
>>
>> I don't have much to say about the patch except that it seems like a good idea...
>>
>> However, some of the terminology could be improved IMO.
>> E.g., "variable type" or "variable font" should be something like
>> variable-width font or proportionally-spaced font.
> 
> Good point.
> 
> I need to be more careful in using terms rarely found in kernel development.
> 
> In this case, "variable font" means "font file which employs the OpenType
> font variations technology".
> 
> There is a Wikipedia page at: https://en.wikipedia.org/wiki/Variable_font
> 

Ah, I see. Thank you.

>>
>> "static ones" should be something like fixed-space fonts or monospaced fonts.
>>
>> Unless I just completely don't understand the uses of "variable" and "static" here.
> 
> "static" here means "non-variable".
> 
> I'll expand the changelog a bit in v2 with your comments in mind.
> 
>         Thanks, Akira

-- 
#Randy

  reply	other threads:[~2024-03-24  0:34 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-23 12:02 [PATCH] docs: Detect variable fonts and suggest removing them Akira Yokosawa
2024-03-23 14:55 ` Randy Dunlap
2024-03-24  0:05   ` Akira Yokosawa
2024-03-24  0:34     ` Randy Dunlap [this message]
2024-03-29 14:35 ` Jonathan Corbet
2024-03-29 15:00   ` Akira Yokosawa
2024-04-06  2:04 ` [PATCH v2] docs: Detect variable fonts and suggest denylisting them Akira Yokosawa
2024-04-10 20:52   ` Jonathan Corbet
2024-04-10 22:57     ` Akira Yokosawa
2024-04-10 23:36       ` Jonathan Corbet

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=d91ec85c-6a44-4b4a-bfe4-b8ad8fa95c01@infradead.org \
    --to=rdunlap@infradead.org \
    --cc=akiyks@gmail.com \
    --cc=corbet@lwn.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=relect@bk.ru \
    /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.