From: ahesford <ahesford@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: New package: font-terminus-ttf-4.49.2
Date: Tue, 07 Mar 2023 13:56:52 +0100 [thread overview]
Message-ID: <20230307125652.Yzh3gvfek6Nk_LscETGgQ30g4AlM8NEU-xwKaT22rOA@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-42598@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 935 bytes --]
New comment by ahesford on void-packages repository
https://github.com/void-linux/void-packages/pull/42598#issuecomment-1458125194
Comment:
From the upstream homepage:
> While this TTF version contains both the original bitmaps from Terminus Font and new scalable outlines, the latter are somewhat ugly (and may have slightly wrong proportions). That is because they are generated automatically from the original bitmaps using [Potrace](http://potrace.sf.net/).
>
>This is not a problem if you use the font in e. g. Java applications, because they will automatically use the bitmaps (which look sharp and crisp), provided that you use a font size that has corresponding bitmaps.
Even the creator seems to think this font offers effectively nothing over the standard bitmap font. How does this square with our [quality requirements](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#package-requirements)?
next prev parent reply other threads:[~2023-03-07 12:56 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-05 13:14 [PR PATCH] " milgra
2023-03-07 12:47 ` [PR REVIEW] " LucasTavaresA
2023-03-07 12:56 ` ahesford [this message]
2023-03-08 10:00 ` milgra
2023-03-08 10:05 ` milgra
2023-03-08 10:09 ` [PR PATCH] [Updated] " milgra
2023-03-08 10:57 ` milgra
2023-03-08 12:29 ` LucasTavaresA
2023-03-08 12:39 ` [PR PATCH] [Updated] " milgra
2023-03-08 12:41 ` milgra
2023-03-28 20:06 ` milgra
2023-03-28 20:30 ` classabbyamp
2023-03-28 20:31 ` abenson
2023-03-28 20:32 ` paper42
2023-03-28 20:32 ` ahesford
2023-03-28 20:32 ` [PR PATCH] [Closed]: " ahesford
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=20230307125652.Yzh3gvfek6Nk_LscETGgQ30g4AlM8NEU-xwKaT22rOA@z \
--to=ahesford@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/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).