From: Pablo Rodriguez <oinos@gmx.es>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: issue with current latest (2020.07.20)
Date: Mon, 20 Jul 2020 15:01:03 +0200 [thread overview]
Message-ID: <ee7e6f1b-2dda-bd3f-2bce-7e4580e1c17f@gmx.es> (raw)
Dear list,
with current latest (LuaTeX 2.06 20200717 + ConTeXt MkIV 2020.07.20
10:48), I cannot open luametatex.pdf (its SHA256 reads
cff8b660b65f4f8c121c170bcd59545c5467a7db02614da137e622ef1c5f3964).
Acrobat for Linux complains about malformed document and Evince doesn’t
display anything. Latest mupdf-gl complains about broken xref (mupdf
complains too):
error: cannot recognize xref format
warning: trying to repair broken xref
warning: repairing PDF document
I experience issues in Windows with current latest:
\starttext
\input zapf
\stoptext
The output PDF document opens in SumatraPDF fine. But in Acrobat DC, no
character is displayed.
Could anyone confirm the issues with current latest?
Many thanks for your help,
Pablo
--
http://www.ousia.tk
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___________________________________________________________________________________
next reply other threads:[~2020-07-20 13:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-20 13:01 Pablo Rodriguez [this message]
2020-07-20 13:13 ` Hans Hagen
2020-07-20 13:41 ` Hans Hagen
2020-07-20 15:11 ` Pablo Rodriguez
2020-07-20 16:58 ` Hans Hagen
2020-07-20 19:44 ` Garulfo
2020-07-20 22:03 ` Pablo Rodriguez
2020-07-20 22:09 ` Otared Kavian
2020-07-21 11:56 ` Hans Hagen
2020-07-21 20:06 ` Pablo Rodriguez
2020-07-20 21:31 ` Pablo Rodriguez
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=ee7e6f1b-2dda-bd3f-2bce-7e4580e1c17f@gmx.es \
--to=oinos@gmx.es \
--cc=ntg-context@ntg.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).