- ntg-context - NTG Mailing Lists

check if inside footnote
by Henning Hraban Ramm 04 Aug '20

04 Aug '20

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 shortcuts for both cases (that call \index with or without processor), but some paragraphs are very confusing (many long footnotes, or footnotes within footnotes), and I could avoid manually analyzing the structure if my macro could determine on its own if it’s called from a footnote. Not-working example: \setupinteraction[state=start] \defineprocessor[kursiv][style=italicface] \define[1]\Idx{\doifmodeelse{*footnote}{\index{#1}}{\index[kursiv->]{kursiv->#1}}#1} \starttext Text --- \index[C]{A}{B}\footnote{Inside\index{FN}}\index{BF} --- \placeregister[index][criterium=all] \stoptext This also shows the text-running-into-footnotes problem with both of my ConTeXt versions: ConTeXt ver: 2020.01.30 14:13 MKIV beta fmt: 2020.4.12 ConTeXt ver: 2020.07.27 16:30 LMTX fmt: 2020.7.28 Hraban

2 3

\emph not working in LMTX (bug?)
by Jairo A. del Rio 04 Aug '20

04 Aug '20

The following crashes with LMTX (current version: 2020.08.03 14:25): \starttext \emph{Hola} \stoptext Log: \emphasiscorrection ->\ifhmode \ifnum \currentgrouptype =\aligngroupcode \else \expandafter \expandafter \expandafter \font_emphasis_look \fi \fi <to be read again> \egroup \egroup l.2 \emph{Hola} Is it a bug? \emph worked for older versions. Thank you in advance. Regards, Jairo

3 3

bug in current latest (2019.10.11 15:57)?
by Pablo Rodriguez 04 Aug '20

04 Aug '20

Hi Hans, the following sample complains about an undefined command with ConTeXt latest (2019.10.11 15:57): \starttext {\em æb} \stoptext I think this might be a bug in LMTX. Many thanks for your help, Pablo -- http://www.ousia.tk

3 3

\fontdimen in LuaMetaTeX
by Marcel Fabian Krüger 04 Aug '20

04 Aug '20

Hi, recent LuaMetaTeX versions no longer automatically resize the fontdimen arrays on assignments. Is there a way to manually resize them or is it necessary to reload a patched font you want more fontdimens? Also, there is an issue with the error message (I guess) for font.setfontdimen: \starttext \directlua{font.setfontdimen(0, 8, 0)} \stoptext gives token call, execute: invalid option '%i' to 'lua_pushfstring' stack traceback: [C]: in function 'font.setfontdimen' [ctxlua]:1: in main chunk 1 \starttext 2 >> \directlua{font.setfontdimen(0, 8, 0)} 3 \stoptext 4 Best regards, Marcel

2 1

Bug with \wordright in LMTX version 2020-08-03 14:25
by Otared Kavian 04 Aug '20

04 Aug '20

Hi Hans, A file which used to be typeset correctly with the previous versions of lmtx, now produces an error. Despite the error message being extremely cryptic: Error ! Missing number, treated as zero I could guess the origin of the bug, which seems to be \wordright, but although the following minimal example shows a bug it does not produce the same ERROR output page: %%%% the square ''end of proof'' \definesymbol[Fin][\mathematics{\square}] \def\qed{\wordright{\symbol[Fin]}} \starttext \startformula a^2 + b^2 = c^2 \stopformula \qed % the problem is here \stoptext In the above example if one adds something before \qed, then the square end-of-proof appears. However in my real file ConTeXt ouputs an error page and says: Error ! Missing number, treated as zero. Best regards: Otared

2 1

Fwd: \emph not working in LMTX (bug?)
by Jairo A. del Rio 04 Aug '20

04 Aug '20

---------- Forwarded message --------- De: Jairo A. del Rio <jairoadelrio6(a)gmail.com> Date: lun., 3 de ago. de 2020 a la(s) 23:05 Subject: Re: [NTG-context] \emph not working in LMTX (bug?) To: Wolfgang Schuster <wolfgang.schuster.lists(a)gmail.com> The following worked some days ago. Now it crashes: \setuphead[chapter][alternative=middle,textstyle=\cap,numbercommand=\WORDS] \setuphead[section][sectionsegments=section,align=middle,textstyle={\bf},conversion=R,numbercommand={\bf}] \setuphead[subsection][numbercommand=,textstyle={\it},sectionsegments=subsection,conversion=n] \starttext \startchapter[title=Dummy chapter] \startsection[title=Dummy section] \startsubsection[title=Dummy subsection] \input knuth \stopsubsection \stopsection \stopchapter \stoptext The log says: \endgroup \22>:157>:middle ...headshownumber \strut \headnumbercontent \par \else \fakeheadnumbercontent \fi \begstrut \headtextcontent \endstrut } \strc_rendering_inject_number_and_text ...def \p_command {\headparameter \c!command }\ifx \p_command \empty \directsetup \currentheadrenderingsetup \else \p_command \headnumbercontent \headtextcontent \fi \strc_rendering_place_head_number_and_text ...}\useheadstyleparameter \c!style \setinlineheadreferenceattributes \strc_rendering_inject_number_and_text }\fi \strc_rendering_stop_placement \strc_sectioning_handle ...onditional \headshownumber \let \getheadnumber \fullheadnumber \strc_rendering_place_head_number_and_text \else \strc_rendering_place_head_text \fi \dostoptagged \strc_sectioning_after_yes \else \ifconditional \c_strc_sectioning_hidden \strc_se... \strc_sectioning_start_named_section ...de \currenthead \headparameter \c!beforesection \the \everybeforehead \strc_sectioning_handle {#1}{#2}{#3} \headparameter \c!insidesection ... I guess it's unrelated to Pablo's issue (\emph works again after the patch). El lun., 3 de ago. de 2020 a la(s) 22:48, Wolfgang Schuster ( wolfgang.schuster.lists(a)gmail.com) escribió: > Jairo A. del Rio schrieb am 04.08.2020 um 03:37: > > The following crashes with LMTX (current version: 2020.08.03 14:25): > > > > > > \starttext > > \emph{Hola} > > \stoptext > > > > Log: > > > > > > \emphasiscorrection ->\ifhmode \ifnum \currentgrouptype =\aligngroupcode > > > > \else \expandafter \expandafter \expandafter \font_emphasis_look \fi \fi > > > > <to be read again> \egroup > > > > \egroup > > > > l.2 \emph{Hola} > > > > Is it a bug? \emph worked for older versions. Thank you in advance. > > Yes and it was already reported by Pablo but don't hesitate report > future bugs. > > https://www.mail-archive.com/ntg-context@ntg.nl/msg95268.html > > Wolfgang >

2 2

lmtx update
by Hans Hagen 03 Aug '20

03 Aug '20

Hi, Sorry for the long mail ... One of the changes in lmtx is that we freeze the properties that determine the paragraph shape as well as breaking into lines in such a way that we have predictable behaviour. As a side effect it can be that existing code (lmtx only) will behave differently (will be fixed when we notice) but also that some low level user tweaking can not work, i.e. they are just ignored, but only when they happen mid paragraph which actually is always debatable anyway. Now, if for some reasom you get unexpected results and can't wait for a fix, you can do this: \forgetparagraphfreezing : disables \setparagraphfreezing : enables (default) Of course it might have other side effects once in lmtx we everywhere expect freezing to be enabled. You can take a snapshot with: \freezeparagraphproperties : snapshot relevant parameters \defrostparagraphproperties : resets snapshot More efficient is snapshotting a subcategory: \updateparagraphproperties : all \updateparagraphpenalties : only penalties \updateparagraphdemerits : other than penalties \updateparagraphshapes : hangindent etc Don't use the low level commands that they use because we take plenty of time to experiment at that level and interfaces might evolve, for instance: \frozen\hangindent 30pt \frozen\hangafter 2 is valid and will likely stay. We're talking of a conceptually rather different approach. Internally the engine is still doing the same things but we can control it a bit differently. Due to the way ConTeXt is set up, we can make such a paradigm shift without too much troubles. I'll wrap up more details in an article later. 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 better, especially those used nested in other mechanisms. A side effect of more control is that we can do other tricks too and we're playing with it (kind of fun). More work in progress concerns paragraph wrappers and that will result in a rewrite of some existing mechanism (generic subsystems with instances), but that might as well go unnoticed. To give an idea of possibilities, here is an example: \definedescription[whatever][alternative=right:bottom] \startwhatever{just a small\\example} \input ward \stopwhatever No one ever requested it so see it an a quick and dirty example but don't hesitate to ask for more anyway (we like an occasional challenge). Anyway, it might take some weeks / iterations before all this settles down and now you can't say that we didn't warn you. So far, 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 -----------------------------------------------------------------

6 13

Notation of the first derivative in mathematical mode (lmtx)
by Fabrice Couvreur 03 Aug '20

03 Aug '20

Hello, I replaced the context engine with the lmtx engine but I find that the derivative symbol is too high regardless of the font used. I mainly use modern and pagella because I type many texts using mathematics: can we correct this problem, Thanks for your help. Fabrice \starttext \startitemize[n] \startitem \math{f'(x)=x²+4x+4} \stopitem \startitem \math{f''(x)=2x+4} \stopitem \stopitemize \stoptext

1 0

Re: [NTG-context] limit of index entries?
by Hans Hagen 02 Aug '20

02 Aug '20

On 8/1/2020 6:08 PM, Henning Hraban Ramm wrote: > > >> Am 01.08.2020 um 14:10 schrieb Hans Hagen <j.hagen(a)xs4all.nl>: >> >> On 8/1/2020 1:54 PM, Henning Hraban Ramm wrote: >>> Hi, >>> my aforementioned person index has more than 600 entries. If I get over ~500, ConTeXt (MkIV, several versions) breaks with >>> ! error (push_node): stack overflow >>> mtx-context | fatal error: return code: 256 >>> Is there a hard limit? Can I change it? >> it might relate to protrusion (which needs to enter nested boxes to determine an edge) but how that then can relate to the number of entries puzzles me, unless we pop too less ... in which case i need to trace (with a mwe) > > I can’t reproduce it with a simple example like > > \setupalign[hanging] > > \starttext > > \placeregister[index][criterium=all] > > \dorecurse{10000}{\par\strut\index{Test\recurselevel}} > > \stoptext > > > \recurselevel is empty in that context, \expanded didn’t help, but I guess we need different entries. > > > Find attached the actual data, reduced to the minimum setup – the problem is indeed \setupalign[hanging]. > > I guess I can omit "hanging" for the index, but of course if would be nice if it would work. it has to do with how you do that index: - you do a lot of \index but you do that in vmode - do, they get collected for the next paragraph - that is done in a robust way which involves packing - eventually you flush with a \strut - so we get deeply nested boxes - and that means trouble for protrusion pre-analysis now, I can try to avoid it but we then can have side effects but we'll see can you try to avoid collecting: \leavevmode \index{...}% make sure no spaces get introduced 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 -----------------------------------------------------------------

2 1

cannot reload font index after luametatex update
by kaddour kardio 02 Aug '20

02 Aug '20

Hi, i am running the latest luametatex 2.07.2 from [aur] repos in my archlinux machine, i got this error when trying to update my font lists (lmtx) ➜ ~ mtxrun --script fonts --reload mtxrun | unknown script 'fonts.lua' or 'mtx-fonts.lua' is it a feature? thanks -- Dr YAHYAOUI Mohamed Kaddour, cardiologue .

2 2