unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Raghav Gururajan <raghavgururajan@disroot.org>
To: Leo Famulari <leo@famulari.name>
Cc: 40708@debbugs.gnu.org
Subject: [bug#40708] gnu: font-gnu-unifont: Unify outputs for fonts.
Date: Mon, 11 May 2020 00:54:05 -0400	[thread overview]
Message-ID: <4f1c21b4-b3f2-b8e0-a434-26a5c1b8d0de@disroot.org> (raw)
In-Reply-To: <20200423160538.GA29046@jasmine.lan>


[-- Attachment #1.1.1: Type: text/plain, Size: 1398 bytes --]

Hi Leo!

Sorry for the delayed response.

> Unifont provides TrueType, PCF, and PSF. It does not have OTF fonts.

That's correct. I was suggesting a scenario of using more than one type. :-)

> 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.

OK. I think of two reasons: 1) If one installs this package with
suggested patch, the user can use unifont for any purpose as they wish.
It may be application (ttf), console/grub (psf) and/or display server
(pcf). 2) The setup will be consistent with other font packages, where
the package installs fonts with all the types it can provide.

> 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.

Improving UI would be good too. Regarding multiple outputs, I think it
is good enough to separate libs, bins and docs. In this packages, we
already separated bin and fonts. I suggest that we shall not separate
fonts further into it's subtypes. That is all I ask. :-)

Regards,
RG.

[-- Attachment #1.1.2: 0xAE6EF3046D6F7B57.asc --]
[-- Type: application/pgp-keys, Size: 2877 bytes --]

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2020-05-11  4:54 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
2020-05-11  4:54       ` Raghav Gururajan [this message]
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=4f1c21b4-b3f2-b8e0-a434-26a5c1b8d0de@disroot.org \
    --to=raghavgururajan@disroot.org \
    --cc=40708@debbugs.gnu.org \
    --cc=leo@famulari.name \
    /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).