[NTG-context] Missing letters and numbers in printout

Pablo Rodriguez oinos at gmx.es
Thu Sep 29 18:10:25 CEST 2022


On 9/29/22 15:54, Angel M Alganza via ntg-context wrote:
> On Wed, Sep 28, 2022 at 03:59:07PM +0200, Hans Hagen via ntg-context wrote:
> [...]
>> but lmtx is and will stay as default
>
> Too bad the default won't work as expected (it did before or, at least
> with TeXLive distribution,) sometimes, for some people or for some of
> their files.

Hi Ángel,

there is nothing that prevents this to be fixed (as far as I know).

TeXLive is still using LuaTeX as default for ConTeXt. This will be
hopefully changed in next release of TeX Live (according to
https://mailman.ntg.nl/pipermail/ntg-context/2022/106829.html by Hans
himself).

The following code relates to an issue I had with ConTeXt myself:

  \setuppapersize[A5][A4, landscape]
  \doifmodeelse{broken-printer}
    {\setuparranging[2UP,doublesided]
     \setupinteractionscreen[option={portrait, paper}]}
    {\setuparranging[2UP]
    \setupinteractionscreen[option={landscape, paper}]}
  \starttext
  \dorecurse{32}
    {\input knuth\par}
  \stoptext

In a copyshop I used to go (more than four years ago), they had a
printer that didn’t understand duplex printing when pages were in
landscape orientation.

The guy of the copyshop was a really nice person, but I didn’t want to
bother him with
https://opensource.adobe.com/dc-acrobat-sdk-docs/standards/pdfstandards/pdf/PDF32000_2008.pdf#search=DuplexFlipShortEdge.

The printout was wrong, since page was flipped on the long edge. Only
the other duplex printing option (besides Simplex) worked with that printer.

The bug was clear on the printer interpreter. I thought of writing to
the printer manufacturer so that they fix their printers. But it wasn’t
worth the effort.

In your case, I don't know why LMTX generated documents misbehave with
the PDF interpreter from your printer. It might be that font embedding
is flawed, or that the interpreter is at fault.

But unless you find out which code is wrong here, you may experience
issues, but there is nothing to fix in this case.

Sorry for repeating myself, but you know way better than mine that this
is code and it requires (a lot of) analysis to find the cause here.

Just in case it helps,

Pablo


More information about the ntg-context mailing list