From: Adonay Felipe Nogueira <adfeno@openmailbox.org>
To: 26659@debbugs.gnu.org
Subject: bug#26659: [contact.ng0@cryptolab.net: Re: fonts bug in icecat?]
Date: Mon, 08 May 2017 15:29:18 -0300 [thread overview]
Message-ID: <871srzb3sx.fsf@openmailbox.org> (raw)
In-Reply-To: <87a86nb6x0.fsf@openmailbox.org> (Adonay Felipe Nogueira's message of "Mon, 08 May 2017 14:22:03 -0300")
Or you can do "the inverse", by doing this:
1. *Do not* install fontconfig from Guix, but make sure to have fontcofig
installed in your foreign distro.
2. Make the file "$XDG_CONFIG_HOME/fontconfig/fonts.conf" with contents:
# Begin of file
<fontconfig>
<dir>~/.guix-profile/share/fonts</dir>
</fontconfig>
# End of file
3. Do:
$ fc-cache -rfv
So, the way I see it is that we have to tell the user that he must make
such "$XDG_CONFIG_HOME/fontconfig/fonts.conf" and choose whether he'll
be using the foreign distro's fontconfig or the fontconfig from Guix,
and chnage this "fonts.conf" file I just mentioned accordingly. If
people agree on, I can contribute with this documentation.
For those willing to explore the issue more: I read the user
documentation for Fontconfig, and it has a variable called
FONTCONFIG_PATH, but it doesn't accept multiple values separated by
colon, it only picks the first value and ignores the rest (I tested it
with `FONTCONFIG_PATH="/etc/fonts:$GUIX_PROFILE/etc/fonts" fc-cache
-rfv` and with `FONTCONFIG_PATH="$GUIX_PROFILE/etc/fonts:/etc/fonts"
fc-cache -rfv` and they resulted differently, but the only common point
was the fonts found inside "$XDG_DATA_HOME/fonts" because both places
referenced in FONTCONFIG_PATH paths have a "fonts.conf" file that has a
part similar to "<dir prefix="xdg">fonts</dir>").
next prev parent reply other threads:[~2017-05-08 18:30 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-25 20:18 bug#26659: [contact.ng0@cryptolab.net: Re: fonts bug in icecat?] Leo Famulari
2017-04-25 20:52 ` ng0
2017-04-26 8:54 ` ng0
2017-04-26 17:17 ` Maxim Cournoyer
2017-04-26 21:05 ` ng0
2017-04-26 21:29 ` Maxim Cournoyer
2017-04-30 20:37 ` Chris Marusich
2017-04-30 20:47 ` ng0
2017-04-30 22:18 ` ng0
2017-04-30 22:28 ` ng0
2017-04-30 22:58 ` ng0
2017-05-08 17:22 ` Adonay Felipe Nogueira
2017-05-08 18:29 ` Adonay Felipe Nogueira [this message]
2017-05-08 18:34 ` Adonay Felipe Nogueira
2017-05-09 8:46 ` ng0
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=871srzb3sx.fsf@openmailbox.org \
--to=adfeno@openmailbox.org \
--cc=26659@debbugs.gnu.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).