From: Eli Zaretskii <eliz@gnu.org>
To: Anand Tamariya <atamariya@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: [Patch] Basic WYSIWYG printing in GNU Emacs
Date: Wed, 11 Aug 2021 14:41:48 +0300 [thread overview]
Message-ID: <83zgtodx8j.fsf@gnu.org> (raw)
In-Reply-To: <CADm7Y4nTmUXhjarAYdsZ2F9EnPFSLXR-3Y7nf3+dBtZypyP=iw@mail.gmail.com> (message from Anand Tamariya on Wed, 11 Aug 2021 10:02:03 +0530)
> From: Anand Tamariya <atamariya@gmail.com>
> Date: Wed, 11 Aug 2021 10:02:03 +0530
> Cc: emacs-devel@gnu.org
>
> Printers use "postscriptname" defined in a font file while searching for fonts. psname.txt provides a sample
> of how to read that information from a font backend. It is not mandatory - but its presence will prevent nasty
> surprises. In its absence, Lisp code uses font file base name. If the file name doesn't match
> postscriptname, printing might fail - "might" because printer will try its best to substitute a suitable font.
> Theoretically, there's no dependency except Ghostscript which does most of the heavy lifting for printing in
> Emacs. Fonts other than Truetype might require additional configuration as defined in Ghostscript manual.
Could you please point to the code which uses or requires Ghostscript,
I don't think I see it in the patch you sent. And since you seem to
be using the HarfBuzz rendering, why do we need Ghostscript at all?
Thanks.
next prev parent reply other threads:[~2021-08-11 11:41 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-10 9:29 [Patch] Basic WYSIWYG printing in GNU Emacs Anand Tamariya
2021-08-10 12:31 ` Eli Zaretskii
2021-08-10 18:12 ` Pankaj Jangid
2021-08-11 3:39 ` Anand Tamariya
2021-08-11 4:32 ` Anand Tamariya
2021-08-11 11:41 ` Eli Zaretskii [this message]
2021-08-11 15:49 ` Anand Tamariya
2021-08-11 16:51 ` Eli Zaretskii
2021-08-11 16:58 ` Eli Zaretskii
2021-08-12 5:34 ` Anand Tamariya
2021-08-12 6:11 ` Eli Zaretskii
2021-08-12 6:45 ` Anand Tamariya
2021-08-12 8:08 ` Eli Zaretskii
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://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83zgtodx8j.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=atamariya@gmail.com \
--cc=emacs-devel@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/emacs.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).