From: Leo Famulari <leo@famulari.name>
To: Raghav Gururajan <raghavgururajan@disroot.org>
Cc: 40708@debbugs.gnu.org
Subject: [bug#40708] gnu: font-gnu-unifont: Unify outputs for fonts.
Date: Thu, 23 Apr 2020 12:05:38 -0400 [thread overview]
Message-ID: <20200423160538.GA29046@jasmine.lan> (raw)
In-Reply-To: <20200422224409.22805bb0.raghavgururajan@disroot.org>
On Wed, Apr 22, 2020 at 10:44:09PM -0400, Raghav Gururajan wrote:
> Not sure about discussion, but it is better to combine fonts and keep just
> binaries separate. Because if a user install unifont to use in their
> applications, not all of them gonna use ttf. Some apps gonna look for otf
> formats. It would be confusing to install three different outputs for get all
> formats.
Unifont provides TrueType, PCF, and PSF. It does not have OTF fonts.
Currently, if a user installs 'font-gnu-unifont' they get TrueType
fonts.
On the other hand, the PSF fonts can be used in the bootloader and the
Linux console, and they are only 68 kilobytes, rather than ~22 megabytes
if you combine all the font outputs. I don't see a compelling reason for
that increase.
If the problem is that packages with multiple outputs are confusing, we
should try to improve the UI, and we shouldn't use multiple outputs if
there isn't a good reason. But this is a case where I think it makes
sense.
next prev parent reply other threads:[~2020-04-23 16:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-19 5:24 [bug#40708] gnu: font-gnu-unifont: Unify outputs for fonts Raghav Gururajan
2020-04-23 2:30 ` Leo Famulari
2020-04-23 2:44 ` Raghav Gururajan
2020-04-23 16:05 ` Leo Famulari [this message]
2020-05-11 4:54 ` Raghav Gururajan
2020-05-11 5:32 ` Raghav Gururajan
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200423160538.GA29046@jasmine.lan \
--to=leo@famulari.name \
--cc=40708@debbugs.gnu.org \
--cc=raghavgururajan@disroot.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).