ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Leah Neukirchen via ntg-context <ntg-context@ntg.nl>
To: ntg-context@ntg.nl
Cc: Leah Neukirchen <leah@vuxu.org>
Subject: Re: LMTX generates PDFs with non-working fonts on real printers
Date: Tue, 04 Oct 2022 12:53:12 +0200	[thread overview]
Message-ID: <87zgebhnc7.fsf@vuxu.org> (raw)
In-Reply-To: <005d126c-73b7-24b2-9c18-4ed02aa4de15@xs4all.nl> (Hans Hagen via ntg-context's message of "Tue, 4 Oct 2022 09:33:46 +0200")

Hans Hagen via ntg-context <ntg-context@ntg.nl> writes:

> On 10/4/2022 4:16 AM, Angel M Alganza via ntg-context wrote:
>> On Mon, Oct 03, 2022 at 07:17:10PM +0200, Leah Neukirchen via
>> ntg-context wrote:
>> 
>>> When I print this "directly" (i.e. sending the raw PDF to the printer)
>>> on a Ricoh MP3053 or on a Samsung CLP-680DW, I just get an empty page.
>> I believe that is the exact same problem I have and that I described
>> a
>> few days ago in my email with subject "Missing letters and numbers in
>> printout".  I have some grids on my document, which gets printed out,
>> but nothing else does.

Another data point: Brother B205 doesn't print it either.
But would all of these use the same licensed PDF renderer...

>>> The PDFs render fine on every PDF reader I could find.
>> Same here.
>> 
>>> PDFs generated directly from Context MKIV from TeXLive 2022 using
>>> LuaTeX 1.5 render fine on these printers.
>>> I've also printed PDFs from pdfTeX in the past fine.
>> Same here.
>> 
>>> Any ideas what I should try to help debug this?
>> I was told that this is the default now, that isn't going to change,
>> and
>> that I could always use LuaTeX instead.  I could also use LaTeX, I
>> guess, but I'd rather keep using ConTeXt at least while my old 32 bits
>> OpenBSD installation works.
> what happens if you include the lmtx pdf in a mkiv document as image

On above Brother B205, this document:

\starttext
\externalfigure[foo.mkxl.pdf]
\stoptext

only prints the page number of the outer document, which is kept in a
seperate font:

NREXLC+LMRoman12-Regular             CID Type 0C       Identity-H       yes yes yes      5  0
CLLXEY+LMRoman12-Regular             CID Type 0C       Identity-H       yes yes yes      8  0

I tried converting the pdf with pdfjam (which uses pdfTeX internally)
before, which probably uses similar mechanisms, and it didn't work
either.

-- 
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
___________________________________________________________________________________

  reply	other threads:[~2022-10-04 10:53 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 [this message]
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
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=87zgebhnc7.fsf@vuxu.org \
    --to=ntg-context@ntg.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).