From: Ulrike Fischer via ntg-context <ntg-context@ntg.nl>
To: ntg-context@ntg.nl
Cc: Ulrike Fischer <news3@nililand.de>
Subject: Re: LMTX generates PDFs with non-working fonts on real printers
Date: Thu, 6 Oct 2022 12:31:19 +0200 [thread overview]
Message-ID: <p4hadtawu3pg$.dlg@nililand.de> (raw)
In-Reply-To: <314ae2a4-71c0-a07b-28fe-2a30f926b7fb@freedom.nl>
Am Tue, 4 Oct 2022 18:09:28 +0200 schrieb Hans Hagen via
ntg-context:
>> Hans, is it possible that LMTX uses some technique that is “too modern”
>> for some built-in PDF interpreter?
> we basically use the old pre 1.6 embedding, same as luatex
I saw that the new code renumbers the glyphs, so it uses 0001, 0002
etc instead of the mix of various slot numbers in luatex. Perhaps
the printers don't like that.
--
Ulrike Fischer
http://www.troubleshooting-tex.de/
___________________________________________________________________________________
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-06 10:31 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
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 [this message]
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='p4hadtawu3pg$.dlg@nililand.de' \
--to=ntg-context@ntg.nl \
--cc=news3@nililand.de \
/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).