unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Efraim Flashner <efraim@flashner.co.il>
To: "Boris A. Dekshteyn" <boris.dekshteyn@gmail.com>
Cc: 49021-done@debbugs.gnu.org
Subject: bug#49021: [PATCH 2/2] gnu: font-terminus: Build Open Type Bitmap.
Date: Mon, 21 Jun 2021 15:20:39 +0300	[thread overview]
Message-ID: <YNCEF701YyCy/A/U@3900XT> (raw)
In-Reply-To: <87pmwmnyvi.fsf@enceladus.provocation.me>

[-- Attachment #1: Type: text/plain, Size: 935 bytes --]

On Wed, Jun 16, 2021 at 05:48:33PM +1200, Boris A. Dekshteyn wrote:
> Hi,
> 
> Efraim Flashner <efraim@flashner.co.il> writes:
> 
> > What do the Open Type Bitmap bits do? Is it actually worth putting it in
> > a separate output or would it make more sense to install it by default?
> 
> As of version 1.44, pango no longer supports bitmap fonts other than
> in Opentype format. So, without the OTB format, you cannot use terminus in pango
> enabled apps (most x apps).
> 
> The package already has a separate output for pcf-8bit, so I decided to
> make a separate output for the OTB format. Which might make sense for users
> without x/wayland environments.
> 

Makes sense to me. (Other) Patch pushed!

-- 
Efraim Flashner   <efraim@flashner.co.il>   אפרים פלשנר
GPG key = A28B F40C 3E55 1372 662D  14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

      reply	other threads:[~2021-06-21 12:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-14 13:27 [bug#49021] [PATCH 1/2] gnu: font-terminus: Update to 4.49.1 Boris A. Dekshteyn
2021-06-14 13:31 ` [bug#49021] [PATCH 2/2] gnu: font-terminus: Build Open Type Bitmap Boris A. Dekshteyn
2021-06-15 18:19   ` Efraim Flashner
2021-06-16  5:48     ` Boris A. Dekshteyn
2021-06-21 12:20       ` Efraim Flashner [this message]

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=YNCEF701YyCy/A/U@3900XT \
    --to=efraim@flashner.co.il \
    --cc=49021-done@debbugs.gnu.org \
    --cc=boris.dekshteyn@gmail.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.
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).