From: zimoun <zimon.toutoune@gmail.com>
To: Marius Bakke <mbakke@fastmail.com>
Cc: Guix Devel <guix-devel@gnu.org>
Subject: Re: [PATCH] gnu: fontconfig: Add replacement with font-dejavu instead of gs-fonts.
Date: Wed, 20 May 2020 14:06:36 +0200 [thread overview]
Message-ID: <CAJ3okZ0tq188cTbzcLjfgOhB0OpZr_0gPqTA+8AJPnSLZPqGQQ@mail.gmail.com> (raw)
In-Reply-To: <20200517145012.21532-1-mbakke@fastmail.com>
Hi Marius,
Thank you for the patch.
I have tried it yet... maybe soon today.
On Sun, 17 May 2020 at 16:51, Marius Bakke <mbakke@fastmail.com> wrote:
> * gnu/packages/fontutils.scm (fontconfig)[replacement]: New field.
> (fontconfig/font-dejavu): New variable.
> ---
> Guix,
>
> This is a hack to make (some) fonts working when users don't have fonts
> specified in their system configuration, and (crucially) places where
> the fontconfig cache may be unavailable such as 'guix pack's.
>
> I'm not sure whether font-dejavu is a good replacement here. Another
> approach could be to convert gs-fonts to TrueType or OpenType format.
Apparently, there is different fonts on master and core-updates, if yes why?
I mean, on my machine -- Guix on the top of Debian with font-dejavu
installed -- why does commit 4bdf4182fe (core-update merge) not
display correctly and the parent commit c81457a588 too but the other
parent commit 23a59b180b displays nicely?
All the best,
simon
next prev parent reply other threads:[~2020-05-20 12:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-17 14:50 [PATCH] gnu: fontconfig: Add replacement with font-dejavu instead of gs-fonts Marius Bakke
2020-05-19 15:50 ` Leo Famulari
2020-05-20 11:28 ` Marius Bakke
2020-05-20 22:59 ` Leo Famulari
2020-05-20 22:00 ` Marius Bakke
2020-05-20 12:06 ` zimoun [this message]
2020-05-20 13:55 ` Marius Bakke
2020-05-20 21:03 ` zimoun
2020-05-20 21:41 ` Marius Bakke
2020-05-20 23:35 ` zimoun
2020-05-21 12:46 ` Marius Bakke
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=CAJ3okZ0tq188cTbzcLjfgOhB0OpZr_0gPqTA+8AJPnSLZPqGQQ@mail.gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=guix-devel@gnu.org \
--cc=mbakke@fastmail.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).