From: Hans Hagen via ntg-context <ntg-context@ntg.nl>
To: Angel M Alganza via ntg-context <ntg-context@ntg.nl>
Cc: Hans Hagen <j.hagen@xs4all.nl>
Subject: Re: Missing letters and numbers in printout
Date: Wed, 28 Sep 2022 15:59:07 +0200 [thread overview]
Message-ID: <490c6d21-3e95-1b82-9e4e-a1fcf79bf0b4@xs4all.nl> (raw)
In-Reply-To: <YzRMkMpLQLe7kmQB@zombi.ugr.es>
On 9/28/2022 3:30 PM, Angel M Alganza via ntg-context wrote:
> On Tue, Sep 27, 2022 at 04:03:06PM +0200, Pablo Rodriguez via
> ntg-context wrote:
>
>> In that case, run "context --luatex --generate" first and then "context
>> --luatex a6lua.tex".
>>
>> This would give you a pure LuaTeX-compiled PDF document.
>>
>> I think that this PDF document will be fine with your printer.
>
> It was. I printed it this morning without any problem. Thank you!
>
> If compiling with --luatex option seem to have more chances to produce a
> complete product, shouldn't it be convenient for this option to be the
> default? I would expect 'context file.tex' to work "out of the box" and
> produce a correct and complete PDF output. Would it be possible to have
> that changed? Or is there maybe any other potentially undesirable side
> effect?
>
> Also, I guess that can be configured somehow so, what would need to be
> changed to have 'context file.txt' to compile using luatex instead of
> LuaMetaTeX?
top line:
% engine=luatex
but lmtx is and will stay as default (btw, you don't run the latest
greatest)
Hans
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
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-09-28 13:59 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
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 [this message]
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=490c6d21-3e95-1b82-9e4e-a1fcf79bf0b4@xs4all.nl \
--to=ntg-context@ntg.nl \
--cc=j.hagen@xs4all.nl \
/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).