From: "Ludovic Courtès" <ludo@gnu.org>
To: Eric Bavier <ericbavier@centurylink.net>
Cc: Help guix <help-guix@gnu.org>, nightowl <nightowl@members.fsf.org>
Subject: Re: printing pdf with evince
Date: Mon, 11 Mar 2019 17:03:27 +0100 [thread overview]
Message-ID: <8736ntv1o0.fsf@gnu.org> (raw)
In-Reply-To: <20190219222352.3601524e@centurylink.net> (Eric Bavier's message of "Tue, 19 Feb 2019 22:23:52 -0600")
Hello,
Eric Bavier <ericbavier@centurylink.net> skribis:
> On Tue, 19 Feb 2019 12:28:35 -0600
> nightowl <nightowl@members.fsf.org> wrote:
>
>> I recently notice that when I try to send a pdf document to the printer
>> using the gnome viewer evince, it will not print text. For comparison,
>> I can also print a pdf document from within the icecat browser, and it
>> works good. Anyone know why evince would behave this way when printing
>> hard copy of text from a pdf? I read that the gnome settings key
>> 'override-restrictions' for org.gnome.Evince schema should be set to
>> 'true' and that is what I currently have by default.
>>
>
> I just noticed this recently on my machine too. Evince does not print
> nor display most (all?) of the nonembedded fonts in several documents
> I've opened. The "document properties" -> "Fonts" window says that
> GuixSD system fonts are being substituted, e.g. the Liberation fonts,
> but they are not displayed.
On a high-end printer with a non-Guix CUPS service running, I can print
just fine. However I’ve seen the problem you describe with a low-end
printer and the CUPS service provided by Guix.
Could it be that our CUPS service somehow fails to find the standard
PostScript fonts, those normally provided by the ‘gs-fonts’ package?
Thanks,
Ludo’.
next prev parent reply other threads:[~2019-03-11 16:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-19 18:28 printing pdf with evince nightowl
2019-02-20 4:23 ` Eric Bavier
2019-02-21 0:32 ` nightowl
2019-03-11 16:03 ` Ludovic Courtès [this message]
2019-02-22 4:01 ` Chris Marusich
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=8736ntv1o0.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=ericbavier@centurylink.net \
--cc=help-guix@gnu.org \
--cc=nightowl@members.fsf.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.
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).