From: Steffen Wolfrum via ntg-context <ntg-context@ntg.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Cc: Steffen Wolfrum <context@st.estfiles.de>
Subject: interwordspace error after update
Date: Mon, 6 Jun 2022 20:12:11 +0200 [thread overview]
Message-ID: <F7D79DEA-0CFE-4E00-834C-4B3708249484@st.estfiles.de> (raw)
Hi,
with my last ConTeXt ver 2022.01.21 20:31 LMTX (arm64) this work:
\startsetups footnotesetup
\interwordspace 2.75pt % \setuptolerance[NEUNspace] hat hier keine Wirkung!
\interwordstretch 1.79999pt
\interwordshrink 0.9pt
\setupinterlinespace[line=11pt, height=.79,depth=.21]
\lineskiplimit-\maxdimen
\setupwhitespace[0pt]
\stopsetups
Now, with ver 2022.05.11 11:36 LMTX (arm64) the same document gives an error:
tex error > tex error on line 4 in file ./01_Fara.tex: You can't use '\scaledinterwordspace' in internal vertical mode
<macro> \22>:footnotesetup
#1->\interwordspace
2.75pt\clubpenalty =10000\widowpenalty =10000\displaywidowpenalty =10000\brokenpenalty =0\setupinterlinespace [line=11pt, height=.79,depth=.21]\lineskiplimit -\maxdimen \setupwhitespace [0pt]
<lua output>
<macro> \m_syst_setups_asked
\clf_autosetups {\m_syst_setups_asked }
\relax
<macro> \handlenoteinsert
...ngroup \edef \currentnote {#1}\strc_constructions_initialize {#1}\strc_notes_synchronize \the \everybeforenoteinsert \insert \currentnoteinsertionnumber \bgroup \the \everyinsidenoteinsert \relax \usesetupsparameter \noteparameter
\useinterline ...
<macro> \currentconstructionsynchronize
...es \global \settrue \postponednote \orelse \ifconditional \c_strc_notes_flushed \handlenoteitself \currentnote \currentnotenumber \orelse \ifconditional \c_strc_notes_delayed \else \handlenoteinsert \currentnote \currentnotenumber
\fi \endgroup ...
<macro> \currentconstructionsynchronize
\csname \??constructionnotehandler \currentconstructionhandler \endcsname
\strc_constructions_finalize \strc_notations_finalize
<line 3.101>
\stopfootnote
}
Is there any chance my setup might work again?
Steffen
___________________________________________________________________________________
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:[~2022-06-06 18:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-06 18:12 Steffen Wolfrum via ntg-context [this message]
2022-06-06 18:34 ` 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=F7D79DEA-0CFE-4E00-834C-4B3708249484@st.estfiles.de \
--to=ntg-context@ntg.nl \
--cc=context@st.estfiles.de \
/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).