place.)
hard to say without knowing what happens before you do the
\externalfigure command
you can put
\tracingall
someplace before it and
\tracingnone
after the \removeunwantesspaces and then check the log and see where a
space is injected
Hans
\operatingsystem \NC\NR
>>> \stoptabulate
>>> \stoptext
>> On MacOS 10.13 the result of \operatingsystem is „osx-ppc“.
>> That was a surprise:-)
> maybe apples are no longer apples
They lost the Power when they became Intelligent, and now they get ARMed.
&
\outputfilename\NC\NR
\NC \type{\operatingsystem} \NC \operatingsystem \NC\NR
\stoptabulate
\stoptext
On MacOS 10.13 the result of \operatingsystem is „osx-ppc“.
That was a surprise:-)
maybe apples are no longer apples
because we cannot check for some env variable directly (at least we
could not
asily build on Debian
8 or 9).
I believe the RPI is currently running some recent version of Ubuntu
(it was set up by Hans; I would need to check to be sure, but it could
well be that it's 20.04).
Indeed, because older 64 bit made the machine freeze after a while. We
run from usb (3) which
equest those binaries before, and this is the
> first complaint I see about the glibc-too-new issue on aarch64 (it was
> common on the Intel platform, but there we can easily build on Debian
> 8 or 9).
>
> I believe the RPI is currently running some recent version of Ubuntu
> (it was
eve the RPI is currently running some recent version of Ubuntu
(it was set up by Hans; I would need to check to be sure, but it could
well be that it's 20.04).
Judging from (random google hits)
https://www.raspberrypi.org/forums/viewtopic.php?t=243985
https://www.raspberrypi.org/blog/lat
On 11/25/2020 6:10 PM, Joseph wrote:
\setupindenting[yes, next, 1em]
\starttext
\input knuth
\stoptext
hm, maybe i did somethign wrong. i'll check it, but indeed for now you
can just use the patch
yntax "\D{Label} description" doesn't print "Label" at all.
The syntax with \start, \stop works fine but has a nasty effect on the next
TABLE if it uses TH (check attached pdf).
This is a different problem which is unrelated
print "Label" at all.
The syntax with \start, \stop works fine but has a nasty effect on the next
TABLE if it uses TH (check attached pdf).
Thank you for your help
PS @Hans, thanks for adding \TB to \startcases, it works perfectly well.
--
Jean-Philippe Rey
jean-philippe@centrales
7;, file 'enco-ini.mkxl', line 315
yes, i'll make new zip btu i also found out that the build server is n't
running so we get the wrong binaries (i kind of assume it runs and
didn't check)
Hans
-
On 11/21/20 11:04 AM, Wolfgang Schuster wrote:
To check whether a stretch or shrink value is set LMTX takes a look at
the next character (p, P, m or M) before it makes a decision, when you
have now a word after \hskip which start with one of these characters
(e.g. Materiam) you trigger the
the file indeed compile again! Any
explanation for the strange behavior of the error?
In LMTX the order of the plus and minus values of \hskip can be written
in any order and it's even possible to set them multiple times (try the
example below with LuaTeX and LMTX).
To check whet
hat quite some code is from more than a decase ago, evolved a bit but seldom changed conceptually). Here's a fix: \unprotect \def\spac_indentation_remove {\ifzeropt\parindent \else \begingroup \unskip % we also need to check for the subtype \setbox\scratchbox\lastbox % we also need to
code
> \unskip % we also need to check for the subtype
> \orelse\ifnum\lastnodetype=\hlistnodecode
> \setbox\scratchbox\lastbox % we also need to check for the subtype
> \else
> % forget about it
> \fi
> \endgroup
> \
ore drastic upgrading ... keep in mind that quite some code is
from more than a decase ago, evolved a bit but seldom changed conceptually).
Here's a fix:
\unprotect
\def\spac_indentation_remove
{\ifzeropt\parindent \else
\begingroup
\unskip % we also need to check for the
Dear Fabrice,
helpful links, thank you very much.
Best wishes,
Tomáš
Tue, Nov 17, 2020 ve 03:42:35PM -0500 Fabrice L napsal(a):
#Hi,
#
#The solution is rather simple, check here:
#[3]https://support.apple.com/en-us/HT202491
#or
#[4]https://support.apple.com/en-ca/guide
perience with MacOS, so I would like to ask for some hints
> how we can fix it.
The solution is rather simple, check here:
https://support.apple.com/en-us/HT202491
<https://support.apple.com/en-us/HT202491>
or
https://support.apple.com/en-ca/guide/mac-help/mh40616/macAfter
<https://
table,frame=on,offset=0.5mm,frameoffset=1mm,type=radio,color=black]
\definefield[test][check][cbox][yes][no]
\starttext
\field[test] \space Do you see the word »yes«?
\stoptext
Unfortunately in Firefox and some other PDF Viewer there is the word
"yes" written in the checkbox.
This
Hello Andrés!
On Wed, 11 Nov 2020 at 01:25, Andres Conrado Montoya Acosta <
ela...@chiquitico.org> wrote:
> may I ask someone, who understands knockout and overprint in the printing
>> press, to check test cases in the attached file from the test suite, if
>> overprint is w
>
> may I ask someone, who understands knockout and overprint in the printing
> press, to check test cases in the attached file from the test suite, if
> overprint is working or not in Mark IV, please?
>
> Regards,
> Jano
>
>
Hi Jano, as far as I can check wi
Hello,
may I ask someone, who understands knockout and overprint in the printing
press, to check test cases in the attached file from the test suite, if
overprint is working or not in Mark IV, please?
Regards,
Jano
On Fri, 30 Oct 2020 at 11:02, Jano Kula wrote:
>
>
> On Thu, 29 Oc
x/context/base/mkiv/.
>
> I created that symlink, because grepping for commands or options is a
> way to learn by reading the code.
>
> Not that I understand the whole, but I see which options are available
> and I can check some samples included.
>
> strc-pag.mkxl is your f
I see which options are available
and I can check some samples included.
strc-pag.mkxl is your friend here. There are three page series. You
could even create more page series (not normally needed).
Pablo
--
http://www.ousia.tk
___
[palatino] don’t seem to
work at all.
Results are different if feature ef1 is defined or not.
It's best to check these things first with \definefont to ensure it
isn't a problem of \definefontfamily.
With all features defined, paragraph width is wrong using
"effect={width=1.0}&q
if feature ef1 is defined or not.
With all features defined, paragraph width is wrong using
"effect={width=1.0}".
Could you check this?
Many thanks for your help,
Pablo
--
http://www.ousia.tk
___
If your q
an older version of Debian for building,
but those don't provide sufficiently recent build tools (cmake, git,
ninja build system, ... I believe that CMake was the main blocker, but
I'm no longer absolutely sure).
By far the easiest solution was to switch from Debian 8 to 9 (or
something
indicates that the
module is loaded. It gives no other clues. The output has a blank line
where the break should be, as shown in the included snips.
I guess it's the same bug (related to a symbol check) as Pablo mentioned
for the itemize environment.
yes, symbol che
other clues. The output has a blank line
where the break should be, as shown in the included snips.
I guess it's the same bug (related to a symbol check) as Pablo mentioned
for the itemize environment.
Wol
at 14pt]
and that fails the same way.
for now rename the file to one with a lowercase suffix (i'll check for
that)
-
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt |
about their dimensions (by using shifts) and i have to check some
mechanisms for that - read: can do them nicer now without guessing
i will hack a solution but eventually will split off the lmtx/mkiv code
for those bits and pieces (takes some time so it will happen after the
flagging effort)
On 11/7/20 11:40 AM, Floris van Manen wrote:
> Dear Hans,
>
> Would it be possible to have a simple text file with the latest release
> version (or date) tag in it? Next to the folder containing the actual
> install script files? In that case it is easy to check that version tag
On 07/11/2020 12:19, Hans Hagen wrote:
a version mismatch normally comes from the fact that i generate an lmtx
update (for wolfgang to check, posted elsewhere) but nor a mkiv one and
then upload to the website (as happened)
also, the update script itself doesn't get updated so when
Hi,
a version mismatch normally comes from the fact that i generate an lmtx
update (for wolfgang to check, posted elsewhere) but nor a mkiv one and
then upload to the website (as happened)
also, the update script itself doesn't get updated so when that gets
adapted one has to get it
Dear Hans,
Would it be possible to have a simple text file with the latest release
version (or date) tag in it? Next to the folder containing the actual
install script files? In that case it is easy to check that version tag
by comparing with the local copy and decide if a further download
n Fri, Nov 6, 2020 at 10:52 PM Aditya Mahajan wrote:
> On Fri, 6 Nov 2020, thierry horsin wrote:
>
> > Hi Ramkumar,
> >
> > Maybe you could have some scripts that check when the JSON file is
> modified
> > and if so launches the compilation. I did that sort
this is my script for a daily update check which seems to do the job
#!/usr/bin/env bash
cd ~/context
context --version | grep "current version"
echo ""
mtxrun --script cache --erase >ctx.log
rm tex/*.tma
sh ./install.sh >ctx.log
context --versi
On Fri, 6 Nov 2020, thierry horsin wrote:
> Hi Ramkumar,
>
> Maybe you could have some scripts that check when the JSON file is modified
> and if so launches the compilation. I did that sort of script in order to have
> a continuous compilation process by checking every second if
Hi Ramkumar,
Maybe you could have some scripts that check when the JSON file is
modified and if so launches the compilation. I did that sort of script
in order to have a continuous compilation process by checking every
second if my current .tex file is modified.
Best
Thierry
On 06/11/2020
ffect.
It does here (not that i have a lib to test) so maybe check your path:
.../tex-context/tex/texmf-win64/bin/lib/luametatex/foo/libfoo.dll
(put the file there and run mtxrun --generate)
The lua versions should match and there shopuld be the initialer function.
\enabletrackers[*lib*]
gives
Sylvain Hubert schrieb am 04.11.2020 um 16:15:
Moreover, is there any way to let context give an error at all when
encountering something like `\setuppagenumbering[position=footer]` ?
ConTeXt has a function to check assignment list for valid keys but
1. The function doesn't work wit
Hi aditya,
> It is possible for you to check on a fresh install of manjaro in a
virtual machine to rule out the possibility that something else in your
system is causing this behavior.
I remember trying context while browsing the wiki before so it should work
normally in a brand new environm
iable way (it was 0% and
remains 0%).
It is possible for you to check on a fresh install of manjaro in a virtual
machine to rule out the possibility that something else in your system is
causing this behavior.
Aditya
__
On 10/14/2020 5:36 PM, Alain Delmotte wrote:
Dear Mojca,
I did just repond to the message without remarking that I was only
answering to you; I'll take care inthe future.
I'll check if the two list are the same, after expanding the condensed
one. And after I'll go to H
Dear Mojca,
I did just repond to the message
without remarking that I was only answering to you; I'll take
care inthe future.
I'll check if the two list are the
same, after expanding the condensed one. And after I'll go to
(if needed we can always have some more advanced mechanism, like wiping
those joiners before kerning happens .. in principle all is doable which
doesn't mean all has to be done)
Just an experiment. I don't know when there will be an update because
first WS and I have to test and doubl
27;t know when there will be an update because
first WS and I have to test and double check some new stuff as we
don't want users to suffer too much from a couple of fundamental new
features.
Is there a patch so the brave can h
e
then is like:
au\discretionary{f-}{-f}{f\zwnj f}asse
\stoptext
Just an experiment. I don't know when there will be an update because
first WS and I have to test and double check some new stuff as we don't
want users to suffer too much from a couple of fu
On 10/8/2020 7:05 PM, Henning Hraban Ramm wrote:
Am 08.10.2020 um 17:41 schrieb Denis Maier :
where can I find the hyphenation patterns used by ConTeXt? I have two wrongly
hyphenated words, and I want to check whether this is due to incorrect
patterns. (I tried the source browser... not
Hi,
where can I find the hyphenation patterns used by ConTeXt? I have two
wrongly hyphenated words, and I want to check whether this is due to
incorrect patterns. (I tried the source browser... not much luck so
far.) The words are:
1. applicable => hyphenated as applic-able
2. obliga
> Am 08.10.2020 um 17:41 schrieb Denis Maier :
>
> where can I find the hyphenation patterns used by ConTeXt? I have two wrongly
> hyphenated words, and I want to check whether this is due to incorrect
> patterns. (I tried the source browser... not much luck so far.) The
want to check whether this is
# due to incorrect patterns. (I tried the source browser... not much
# luck so far.) The words are:
# 1. applicable => hyphenated as applic-able
# 2. obligated => hyphenated as oblig-ated
#
# I know I can use \hyphenation to correct that, but I wanted to check
>
>>\definefontsynonym[ZapfDingbats][file:ZapfDingbats][features=dingbats]
>>I don't know what the previous line does ... but it works ok here when
>>you remove it.
>> This line loads the font from a file ZapfDingbats.ttf. Without this line I
>> get no check m
what the previous line does ... but it works ok here when
you remove it.
This line loads the font from a file ZapfDingbats.ttf. Without this line
I get no check marks in the output and the following log messages:
i don't know that one
fonts > defining > font with asked nam
This line loads the font from a file ZapfDingbats.ttf. Without this line I
get no check marks in the output and the following log messages:
fonts > defining > font with asked name 'uzdr' is not found using
lookup 'file'
fonts > defining > unknown f
>>> n:a105 : \getglyph{ZapfDingbats}{\tochar{n:a105}} \par
>>>
>>> Thank you Hans!
>>> Access by glyph index with \tochar{i:19} works well for both MKIV and
>>> LMTX. Access by name with \tochar{n:a39} does not work in LMTX with log
>>>
>>>going on (i'll look at that)
>>>>
>>>>For nwo access by 'name' or 'index' (these are kind of stable for
>>> such
>>>>an old font):
>>>>
>>>> n:a34 : \getglyph{ZapfDingbats}{
8 : \getglyph{ZapfDingbats}{\tochar{i:48}} \par
> i:49 : \getglyph{ZapfDingbats}{\tochar{i:49}} \par
> n:a104 : \getglyph{ZapfDingbats}{\tochar{n:a104}} \par
> n:a105 : \getglyph{ZapfDingbats}{\tochar{n:a105}} \par
>
> Thank you Hans!
> Access by
dfont[name:ZapfDingbats]✓
\stoptext
I still get no check mark in the output PDF and a log message "char ✓
(U+02713) in font 'ZapfDingbats-4' with id 8: missing". Am I using the
font wrongly?
(This has not a high priority for me, because I have the unified access
by
; > Also \ShowCompleteFont does not report any glyph names in LMTX.
> should be a bit better in yesterdays upload (i also changed the file
> name alias so that in pinciple unicode should work too)
Dear Hans,
Thank you for working on this. I have tried version 2020.09.20: Unicode
input wo
Thanks. I'll need to check what happens here.
Am 19.09.2020 um 12:03 schrieb Hans Hagen:
On 9/18/2020 11:10 PM, denis.maier.li...@mailbox.org wrote:
Hi
Is there a setting that prevents footnotes from spreading over more than
one page? I have a document where this seems to be the case,
7; with id 8: missing
(2) \getglyphdirect{ZapfDingbats}{983059} % LMTX log: char
(U+F0013) in font 'ZapfDingbats-4' with id 8: missing
\ShowCompleteFont{name:ZapfDingbats}{14pt}{1}
\stoptext
In MKIV, line (1) fails to output the requested glyph, while line (2)
produces a "
pfDingbats}{983059} % LMTX log: char (U+F0013)
in font 'ZapfDingbats-4' with id 8: missing
\ShowCompleteFont{name:ZapfDingbats}{14pt}{1}
\stoptext
In MKIV, line (1) fails to output the requested glyph, while line (2)
produces a "check" (✓). In LMTX, line (2) fails and line (1)
works correctly. So, it appears to be an issue with font name to
filename mapping.
I'll try a clean install on a docker image and check it that works ... or just
wait for the newer version, which often fixes such things :-)
there have been no fundamental changes, but the names of these liber*
fo
and it works correctly. So, it appears to be an issue with font name to
filename mapping.
I'll try a clean install on a docker image and check it that works ... or just
wait for the newer version, which often fixes such things :-)
Aditya
___
do I need to make to
accommodate the following? Possibly an \else statement, but not sure
how to include that:
\startchapter [title={Chapter title}] [author={Author Name}]
I forgot to change the argument for the check off the author entry,
this should fix it.
\define[3]\ChapterListCo
o the \ChapterListCommand do I need to make to accommodate
the following? Possibly an \else statement, but not sure how to include
that:
\startchapter [title={Chapter title}] [author={Author Name}]
I forgot to change the argument for the check off the author entry, this
should fix it.
\def
And that’s what the wiki entry is about and what I can tell.
> Just know that when you say (in the new wiki addition) 'check on
> \rawstructurelistuservariable' that link simply tells me 'There is currently
> no text in this page'. That leaves someone like me wit
Thanks, and I am sure that this entry into the wiki will be also helpful
for others. For me it will be step by step, and using your information I
can now at least get an author's name into the toc! But that's about
all. Just know that when you say (in the new wiki addition)
Il 04/09/20 11:01, Henning Hraban Ramm ha scritto:
Am 03.09.2020 um 13:32 schrieb mf :
Use check=yes
But I need check=no, because my author has several entries like
Miller, Carolyne, born Princess of Sayn-Wittgenstein 123–125
Sayn-Wittgenstein, Carolyne of see Miller, Carolyne
i.e
> Am 03.09.2020 um 13:32 schrieb mf :
>
> Use check=yes
But I need check=no, because my author has several entries like
Miller, Carolyne, born Princess of Sayn-Wittgenstein 123–125
Sayn-Wittgenstein, Carolyne of see Miller, Carolyne
i.e. the reference target often has a
On 9/3/20 8:09 PM, Hans Hagen wrote:
> On 9/3/2020 4:52 PM, Pablo Rodriguez wrote:
>> [...]
>> I’m afraid that packed item lists are misbehaving.
>>
>> Could anyone confirm this?
> can you check again (new lmtx)
Many thanks for the new upload, Hans.
Now packed
]
\startitem Item\stopitem
\startitem Item\stopitem
\startitem Item\stopitem
\startitem Item\stopitem
\stopitemize
\stoptext
I’m afraid that packed item lists are misbehaving.
Could anyone confirm this?
can you check again (new lmtx)
Hans
ndex{passim->Ramm, Hraban}{}
No, this results in
"Ramm, Hraban passim see passim"
Only with check=yes, otherwise it works right.
And
\index{passim->Ramm, Hraban}
results in
"Ramm, Hraban passim 1"
No, see attachment page 2.
I.e. I’m still looking for an index entry wi
an passim see passim"
And
\index{passim->Ramm, Hraban}
results in
"Ramm, Hraban passim 1"
I.e. I’m still looking for an index entry without "see" or page number.
> \placeindex[check=no]
This is essential for references to not (exactly
This should be exactly what you asked for:
\defineprocessor[passim][right=\quad{\it passim}]
\starttext
\samplefile{ward}\index{Ward, Peter}
\samplefile{sapolsky}\index{Sapolsky, Robert}
\seeindex{passim->Ramm, Hraban}{}
\seeindex{Hraban}{Ramm, Hraban}
\page
\placeindex[check=yes]
\p
{Ward, Peter}
\samplefile{sapolsky}\index{Sapolsky, Robert}
\seeindex{Ramm, Hraban}{}
\seeindex{Hraban}{Ramm, Hraban}
\page
\placeindex[check=yes]
\page
\placeindex[check=no]
\stoptext
Massi
___
If your question
xis={weight=200}]
\definefont
[sourcelight]
[file:SourceCodeVariable-Roman.otf*light]
\starttext
\sourcelight Hallo
\stoptext
Thanks. I'll check it. (Reminds me to check another issue in a variable
font that I observed recently, something with accuracy, but of could
also be a border
in the math mode,
but I'll have to go back and check the implementation details.
Aditya
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-context@ntg.nl / h
cannot read "between the lines" on
morning reports and therefore miss the point many times. \stopitem
\startitem Too few hours to do adequate offset well record check
\stopitem
\stopachoices
\stopquestion
\startquestion If the toolpusher noted the following tre
ersion > 2020.08.14 18:27
yes, i noticed and will reupload (a rare case actually, two files
updated with overflowing the minutge but it might be why we sometimes
have issues so i now check it)
Hans
-
13:04:52 MESZ schrieb Hans Hagen :
>
> On 8/14/2020 11:41 AM, Jannik Voges wrote:
>
> Hello Pablo,
>
>
> thank you for your suggestions, but I don't use LMTX
> productively, so I
> have no problem with a broken LMTX-version. I
Hello Pablo,
thank you for your suggestions, but I don't use LMTX productively, so I
have no problem with a broken LMTX-version. I only use it to check
whether there are breaking changes in LMTX by typesetting all of my
documents with the newest LMTX-version (to see if I need to change th
Hello Pablo,
thank you for your suggestions, but I don't use LMTX productively, so I
have no problem with a broken LMTX-version. I only use it to check
whether there are breaking changes in LMTX by typesetting all of my
documents with the newest LMTX-version (to see if I need to change th
our suggestions, but I don't use LMTX productively, so
>I
>> have no problem with a broken LMTX-version. I only use it to check
>> whether there are breaking changes in LMTX by typesetting all of my
>> documents with the newest LMTX-version (to see if I need to change
>them
>&g
On 8/14/2020 11:41 AM, Jannik Voges wrote:
Hello Pablo,
thank you for your suggestions, but I don't use LMTX productively, so I
have no problem with a broken LMTX-version. I only use it to check
whether there are breaking changes in LMTX by typesetting all of my
documents with the newest
Pablo Rodriguez schrieb am 13.08.2020 um 16:18:
On 8/13/20 3:11 PM, Wolfgang Schuster wrote:
[...]
With the options "split=no" and "split=repeat" ConTeXt puts the table in
a \vbox but with "split=yes" this doesn't happen.
To check is this is the prob
On 8/13/20 3:11 PM, Wolfgang Schuster wrote:
> [...]
> With the options "split=no" and "split=repeat" ConTeXt puts the table in
> a \vbox but with "split=yes" this doesn't happen.
>
> To check is this is the problem he can put the table in a float
things in ConTeXt can trigger an implicit horizontal context.
With the options "split=no" and "split=repeat" ConTeXt puts the table in
a \vbox but with "split=yes" this doesn't happen.
To check is this is the problem he can put the table in a float
en
and check again.
Wolfgang
___
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
On 6 Aug 2020, at 21:30, Hans van der Meer wrote:
>>
>> This MWE is an example of strange font behaviour according to the log and I
>> do not understand what is causing it.
>> ConTeXt complains "check count_components with mkiv" when the word 'suffi'
On 8/7/2020 9:29 AM, Taco Hoekwater wrote:
On 6 Aug 2020, at 21:30, Hans van der Meer wrote:
This MWE is an example of strange font behaviour according to the log and I do
not understand what is causing it.
ConTeXt complains "check count_components with mkiv" when the word
> On 6 Aug 2020, at 21:30, Hans van der Meer wrote:
>
> This MWE is an example of strange font behaviour according to the log and I
> do not understand what is causing it.
> ConTeXt complains "check count_components with mkiv" when the word 'suffi' i
This MWE is an example of strange font behaviour according to the log and I do not understand what is causing it.ConTeXt complains "check count_components with mkiv" when the word 'suffi' is present (see log message below).Now comes the most strange: remove 'suffi'
le below shows a
> better method.
>
> 2. What you do with \doifelse{...}{even} is to compare the numeric value of
> the section with the string "even" which is always false. To check whether
> the value is odd or even you have to use the \ifodd command.
>
>>
to compare the numeric value
of the section with the string "even" which is always false. To check
whether the value is odd or even you have to use the \ifodd command.
What to change in order to get the desired result?
begin example
\startsetups [section:odd]
\vfill
\bo
On 8/4/2020 1:47 PM, Henning Hraban Ramm wrote:
Am 04.08.2020 um 13:20 schrieb Hans Hagen :
On 8/4/2020 11:04 AM, Henning Hraban Ramm wrote:
Hi, me again...
Is there a check if a macro is called from inside of a footnote, like a system
mode *footnote?
(Same with captions?)
In my current
> Am 04.08.2020 um 13:20 schrieb Hans Hagen :
>
> On 8/4/2020 11:04 AM, Henning Hraban Ramm wrote:
>> Hi, me again...
>> Is there a check if a macro is called from inside of a footnote, like a
>> system mode *footnote?
>> (Same with captions?)
>> In my cu
On 8/4/2020 11:04 AM, Henning Hraban Ramm wrote:
Hi, me again...
Is there a check if a macro is called from inside of a footnote, like a system
mode *footnote?
(Same with captions?)
In my current project, index entries should get italic page numbers if they
occurr inside of a footnote (or a
Hi, me again...
Is there a check if a macro is called from inside of a footnote, like a system
mode *footnote?
(Same with captions?)
In my current project, index entries should get italic page numbers if they
occurr inside of a footnote (or a caption, but that is rare).
I’m using different
On Fri, 31 Jul 2020, Hans Hagen wrote:
Thanks for the update.
Other work in progress is: better columns in itemize, esp proper
footnote support (not that I ever need that but I know users do so ...),
experiments work ok, but I need to check spacing. In general, footnotes
(will) behave a bit
901 - 1000 of 4752 matches
Mail list logo
