From: Leah Neukirchen via ntg-context <ntg-context@ntg.nl>
To: Hans Hagen <j.hagen@xs4all.nl>
Cc: Leah Neukirchen <leah@vuxu.org>,
mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: LMTX generates PDFs with non-working fonts on real printers
Date: Tue, 04 Oct 2022 14:35:52 +0200 [thread overview]
Message-ID: <87sfk3hil3.fsf@vuxu.org> (raw)
In-Reply-To: <9c60ee11-89fb-f833-27cd-f7a0862406fa@xs4all.nl> (Hans Hagen's message of "Tue, 4 Oct 2022 13:54:10 +0200")
Hans Hagen <j.hagen@xs4all.nl> writes:
> what is sent to the printer .. maybe not pdf but something the printer
> driver produces
For the Ricoh and Samsung printers, we printed the raw PDF directly
over JetDirect (port 9100). For the Brother, the "upload PDF"
function was used. So no outside printer drivers involved.
If I run it through Ghostscript, that somehow fixes it:
gs -dPDF -dBATCH -dNOPAUSE -sDEVICE=pdfwrite -sOutputFile=print.pdf foo.pdf
But Ghostscript also seems to rewrite the font, at least in FontForge
it shows a different scale.
Are there any tools to analyze this CID font stream?
--
Leah Neukirchen <leah@vuxu.org> https://leahneukirchen.org
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage : https://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : https://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2022-10-04 12:35 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-03 17:17 Leah Neukirchen via ntg-context
2022-10-03 18:57 ` Leah Neukirchen via ntg-context
2022-10-05 16:02 ` Pablo Rodriguez via ntg-context
2022-10-05 21:25 ` Hans Hagen via ntg-context
2022-10-03 21:57 ` Hans Hagen via ntg-context
2022-10-03 22:34 ` Leah Neukirchen via ntg-context
2022-10-04 2:16 ` Angel M Alganza via ntg-context
2022-10-04 7:33 ` Hans Hagen via ntg-context
2022-10-04 10:53 ` Leah Neukirchen via ntg-context
2022-10-04 11:54 ` Hans Hagen via ntg-context
2022-10-04 12:35 ` Leah Neukirchen via ntg-context [this message]
2022-10-04 12:50 ` Hans Hagen via ntg-context
2022-10-04 12:54 ` Hans Hagen via ntg-context
2022-10-04 15:52 ` Leah Neukirchen via ntg-context
2022-10-04 16:29 ` Hans Hagen via ntg-context
2022-10-04 12:59 ` Hans Hagen via ntg-context
2022-10-04 15:44 ` Henning Hraban Ramm via ntg-context
2022-10-04 16:11 ` Hans Hagen via ntg-context
2022-10-04 17:23 ` Henning Hraban Ramm via ntg-context
2022-10-04 11:59 ` Henning Hraban Ramm via ntg-context
2022-10-04 13:21 ` Angel M Alganza via ntg-context
2022-10-04 16:03 ` Henning Hraban Ramm via ntg-context
2022-10-04 16:09 ` Hans Hagen via ntg-context
2022-10-06 10:31 ` Ulrike Fischer via ntg-context
2022-10-06 11:23 ` Hans Hagen via ntg-context
2022-10-06 12:42 ` Leah Neukirchen via ntg-context
2022-10-06 14:23 ` Hans Hagen via ntg-context
2022-10-06 16:42 ` Leah Neukirchen via ntg-context
2022-10-09 6:03 ` Max Chernoff via ntg-context
2022-10-09 10:08 ` Hans Hagen via ntg-context
2022-10-11 19:07 ` Leah Neukirchen via ntg-context
2022-10-12 4:41 ` Aditya Mahajan via ntg-context
2022-10-12 4:56 ` Max Chernoff via ntg-context
2022-10-12 11:14 ` Leah Neukirchen via ntg-context
2022-10-12 22:50 ` Max Chernoff via ntg-context
2022-10-13 17:41 ` Pablo Rodriguez via ntg-context
2022-10-13 18:36 ` Henning Hraban Ramm via ntg-context
2022-10-13 20:35 ` Hans Hagen via ntg-context
2022-10-13 20:32 ` Hans Hagen via ntg-context
2022-10-13 19:30 ` Willi Egger via ntg-context
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87sfk3hil3.fsf@vuxu.org \
--to=ntg-context@ntg.nl \
--cc=j.hagen@xs4all.nl \
--cc=leah@vuxu.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 NNTP newsgroup(s).