From: Henning Hraban Ramm <texml@fiee.net>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: [NTG-context] font error in float placement?
Date: Sat, 13 Jan 2024 19:43:01 +0100 [thread overview]
Message-ID: <9a444efb-d40d-4377-8221-db444d489bb8@fiee.net> (raw)
(LMTX, latest beta with self-compiled binary on OSX-intel.)
With my book, I run into an Lua error while placing a sidefloat.
If I comment \externalfigure or replace the image with a different one,
the error disappears.
I can’t reproduce it in a minimal example, so I guess it depends on the
current surroundings.
Since it points to some font handling and the figure is a PDF containing
fonts, I guess it might depend on the new handling of fonts in PDFs, but
it doesn’t change regardless of
\setupexternalfigures[compact=preset:merge] or other settings.
Here’s the image:
https://yemaya.fiee.net/s/8TqwfcP7mLMmy9p
(In a simple document it works.)
Hraban
"""
lua error > lua error on line 516 in file de/c_feinheiten.tex:
registered function call [1565]:
...xmf-context/tex/context/base/mkxl/lpdf-fix-imp-fonts.lmt:596: attempt
to index a nil value (field 'embed')
stack traceback:
...xmf-context/tex/context/base/mkxl/lpdf-fix-imp-fonts.lmt:596: in
local 'handler'
...xmf-context/tex/context/base/mkxl/lpdf-fix-imp-fonts.lmt:709: in
upvalue 'plugin'
...xmf-context/tex/context/base/mkxl/lpdf-fix-imp-fonts.lmt:938: in
upvalue 'lpdf_epdf_fontplugin'
[string "local lpdf_epdf_fontplugin = lpdf.epdf.fontpl..."]:3: in local
'runner'
...-10/tex/texmf-context/tex/context/base/mkxl/lpdf-fix.lmt:97: in
upvalue 'lpdf_epdf_contentplugin'
[string "local lpdf_epdf_contentplugin = lpdf.epdf.con..."]:3: in local
'runner'
...-10/tex/texmf-context/tex/context/base/mkxl/lpdf-fix.lmt:119: in
field 'pageplugin'
...-10/tex/texmf-context/tex/context/base/mkxl/lpdf-pde.lmt:1371: in
upvalue 'copypage'
...-10/tex/texmf-context/tex/context/base/mkiv/grph-chk.lua:112: in
function <...-10/tex/texmf-context/tex/context/base/mkiv/grph-chk.lua:97>
...-10/tex/texmf-context/tex/context/base/mkxl/grph-inc.lmt:1680: in
function <...-10/tex/texmf-context/tex/context/base/mkxl/grph-inc.lmt:1665>
(...tail calls...)
506 \startsubsection[title=Schriftwahl]
…
513
514 \startplacefigure[title={Beispiele für gebrochene Schriften,
halbherzig von Hand ausgeglichen},location=right,reference=abb:fraktur]
515 \externalfigure[gebrochene_schriften][width=.5\textwidth]
516 >> \stopplacefigure
"""
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl
webpage : https://www.pragma-ade.nl / https://context.aanhet.net (mirror)
archive : https://github.com/contextgarden/context
wiki : https://wiki.contextgarden.net
___________________________________________________________________________________
next reply other threads:[~2024-01-13 18:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-13 18:43 Henning Hraban Ramm [this message]
2024-01-13 20:09 ` [NTG-context] " Henning Hraban Ramm
2024-01-13 20:29 ` Henning Hraban Ramm
2024-01-14 13:02 ` Bruce Horrocks
2024-01-14 13:12 ` 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=9a444efb-d40d-4377-8221-db444d489bb8@fiee.net \
--to=texml@fiee.net \
--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).