ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Pablo Rodriguez via ntg-context <ntg-context@ntg.nl>
To: Angel M Alganza via ntg-context <ntg-context@ntg.nl>
Cc: Pablo Rodriguez <oinos@gmx.es>
Subject: Re: Missing letters and numbers in printout
Date: Mon, 26 Sep 2022 19:10:40 +0200	[thread overview]
Message-ID: <ce0000bc-40af-e110-1b55-68ae9d9c2661@gmx.es> (raw)
In-Reply-To: <YzGx1WCTxRrbUq2n@zombi.ugr.es>

On 9/26/22 16:06, Angel M Alganza via ntg-context wrote:
> Hello,

Hi Ángel,

> [...]
> I tried printing the same file (from the same USB drive) into a
> different printer, this time connected to a computer, and sending the
> file from it, which worked just fine.  My guess is that the first
> printer in missing the font the document uses, whereas the second
> printer received the font from the computer (Devuan Linux), which has
> the appropriate font.  Could that be correct?

From my experience, this is possible, but maybe not highly probable.

By default, ConTeXt includes fonts by default, as far as I can remember
(I have been using it for over a decade).

> In all previous ocasions I used the version of ConTeXt included in
> Texlive on Devuan, but a few months ago I decided to install ConTeXt
> using the official distribution instead.  Could that explain the change
> in behaviour I'm seeing?  Could it be that the previous versions I used
> somehow embeded the fonts into the PDF file but the current one doesn't?

Again, I’d very surprised if that were the case.

BTW, is TeX Gyre Heros the font with missing chars in the printed
version of your PDF document?

I think that your printer is having issues with the embedded font in
your PDF document.

There might be a workaround (or a way of testing this), compiling the
PDF document with LuaTeX instead of with LuaMetaTeX.

If you compile it invoking "context source.tex", use "context --luatex
source.tex".

It might be that your printer has problems with the way LuaMetaTeX
embeds the fonts in the PDF (while it has none with LuaTeX).

But the way to know for sure which tools generated your PDF document and
whether fonts are embedded, "pdfinfo your-file.pdf" and "pdffonts
your-file.pdf" are your friends.

Both infos for the following source:

  \setupbodyfont[helvetica]
  \starttext
  \input zapf
  \stoptext

$ pdffonts a.pdf
name                  type         encoding     emb sub uni object ID
--------------------- ------------ ------------ --- --- --- ---------
TeXGyreHeros-Regular  CID Type 0C  Identity-H   yes yes yes      1  0

$ pdfinfo a.pdf
Title:          a
Creator:        LuaMetaTeX 2.10 20220918 + ConTeXt LMTX 2022.09.11 20:44
Producer:       LuaMetaTeX-2.10
CreationDate:   Mon Sep 26 18:29:02 2022 CEST
ModDate:        Mon Sep 26 18:29:02 2022 CEST
Tagged:         no
UserProperties: no
Suspects:       no
Form:           none
JavaScript:     no
Pages:          1
Encrypted:      no
Page size:      595.276 x 841.89 pts (A4)
Page rot:       0
File size:      7531 bytes
Optimized:      no
PDF version:    1.7

Otherwise, the only option about your documents is guessing.

Just in case it might help,

Pablo



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

  parent reply	other threads:[~2022-09-26 17:10 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-26 14:06 Angel M Alganza via ntg-context
2022-09-26 14:54 ` Hans Hagen via ntg-context
2022-09-26 15:39   ` Angel M Alganza via ntg-context
2022-09-26 17:10 ` Pablo Rodriguez via ntg-context [this message]
2022-09-26 18:26   ` Angel M Alganza via ntg-context
2022-09-26 20:44     ` Hans Hagen via ntg-context
2022-09-26 21:04       ` Angel M Alganza via ntg-context
2022-09-26 21:13         ` Hans Hagen via ntg-context
2022-09-27 14:08         ` Pablo Rodriguez via ntg-context
2022-09-26 21:06     ` Hans Hagen via ntg-context
2022-09-27 14:03     ` Pablo Rodriguez via ntg-context
2022-09-27 17:45       ` Angel M Alganza via ntg-context
2022-09-28 13:30       ` Angel M Alganza via ntg-context
2022-09-28 13:59         ` Hans Hagen via ntg-context
2022-09-29 13:54           ` Angel M Alganza via ntg-context
2022-09-29 14:06             ` Hans Hagen via ntg-context
2022-09-29 16:10             ` Pablo Rodriguez via ntg-context
2022-09-28 15:10         ` Pablo Rodriguez via ntg-context
2022-09-28 15:20           ` Hans Hagen 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=ce0000bc-40af-e110-1b55-68ae9d9c2661@gmx.es \
    --to=ntg-context@ntg.nl \
    --cc=oinos@gmx.es \
    /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).