unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Marius Bakke <mbakke@fastmail.com>
To: Ivan Kozlov <kanichos@yandex.ru>, 39602@debbugs.gnu.org
Subject: [bug#39602] Generate font catalogues for the X server
Date: Mon, 22 Jun 2020 22:11:01 +0200	[thread overview]
Message-ID: <87k0zyc14a.fsf@gnu.org> (raw)
In-Reply-To: <2060961581700625@iva4-64850291ca1c.qloud-c.yandex.net>

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

Ivan Kozlov <kanichos@yandex.ru> writes:

> Actually, I am sending this as a patch.
>
> This should produce a "share/fontpath.d" directory in the profile which is a font catalogue as described in Xserver(1). Then the X server font path can be set to include this catalogue and it will find the installed fonts. This concerns all legacy X11 applications using the core fonts system, and most importantly xterm.
>
> The hook ‘fonts-dir-file’ was originally added for this purpose as the comments can tell; you would include e. g. "share/fonts/X11/misc" from the profile in the font path, which is a union directory with symbolic links to fonts that want to install there and a fonts.dir file describing all of them. This has not been working for ages, since the X.org server stopped following symbolic links to font files for security reasons. It should be removed.

Thanks for this investigation, and the patch!

Overall it LGTM, but I wonder how useful it is, seeing as no one has
reported the issue.  Would it make sense to add hooks in the
configuration system instead for setting font path and a font union?

A patch to remove the legacy broken 'fonts-dir-file' generation from
(guix profiles) would be welcome, by the way.

Thanks,
Marius

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

      parent reply	other threads:[~2020-06-22 20:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-14 17:17 [bug#39602] Generate font catalogues for the X server Ivan Kozlov
2020-06-12 18:44 ` Ivan Kozlov
2020-06-22 20:11 ` Marius Bakke [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=87k0zyc14a.fsf@gnu.org \
    --to=mbakke@fastmail.com \
    --cc=39602@debbugs.gnu.org \
    --cc=kanichos@yandex.ru \
    /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).