- ntg-context - NTG Mailing Lists

PNG image inclusion resolution
by Christoph Reller 02 Sep '20

02 Sep '20

Dear List, I am using ConTeXt LMTX 2020.08.31 22:16. Consider the following MWE: \starttext \externalfigure[resolutionTest.png] \stoptext When comparing the output with ConTeXt MKIV, then the image size is extremely small. gimp reports the resolution of resolutionTest.png as 71.984 DPI. Is this a bug? (I cannot reproduce the shrinkage with hacker.png.) Also, I noticed that the "resolution" key when applied as: \externalfigure[resolutionTest.png][resolution=150] has no effect. What is the meaning of this key? Cheers, Christoph

2 2

Tagged PDFs from Context
by Karl Pettersson 02 Sep '20

02 Sep '20

Hi See this discussion. https://github.com/jgm/pandoc/issues/5409#issuecomment-678781349 Would it be possible to generate PDFs with headings tagged like H1, H2, H3, H4..., instead of using the H tag for all levels, which seems to be required for proper rendering with some screenreaders? It seems to me that it would require modfications to the Context source code. https://source.contextgarden.net/tex/context/base/mkiv/strc-tag.lua Any ideas? Best regards Karl Pettersson

3 2

Import a metapost extension
by Fabrice Couvreur 02 Sep '20

02 Sep '20

Hello Is it possible to import a metapost extension into a file compiled with the lmtx engine ? I tried unsuccessfully with this example : %%%% begin test.tex \starttext \startMPcode input mp-scratch; Scratchversion:=3; draw Drapeau; draw Repeter("4"); draw Avancer("50"); draw Tournerd("90"); draw FinBlocRepeter; \stopMPcode \stoptext %%%% end test.tex Thanks Fabrice

4 6

strange behavior with \groupedcommand in recent versions of LMTX
by mf 02 Sep '20

02 Sep '20

Hello list, this is a MWE that worked right in MkIV and in LMTX versions (at least) until April 22nd, 2020. There's a macro, \wordorparagraphright, that takes one argument, makes a hbox with it and measures its width - if its width is less than \hsize, then it calls \wordright - if its width is more than \hsize, then it ends the current paragraph and starts a right-aligned paragraph with the argument There are two implementations in the MWE: one is through \groupedcommand, and that's the one that worked once and doesn't now. ---------------------------------------------------- \unexpanded\def\groupedwordorparagraphright{\dosingleempty\dogroupedwordorparagraphright} \def\dogroupedwordorparagraphright[#1]{\groupedcommand{\setbox\scratchbox\hbox\bgroup} {\egroup\ifdim\wd\scratchbox < \hsize \wordright{\unhbox\scratchbox} \else \par\penalty10000 \startalignment[flushright]\unhbox\scratchbox\stopalignment \fi}} \unexpanded\def\wordorparagraphright#1{% \setbox\scratchbox\hbox{#1} \ifdim\wd\scratchbox < \hsize \wordright{#1} \else \par\penalty10000 \startalignment[flushright]\unhbox\scratchbox\stopalignment \fi} \starttext \type{\wordorparagraphright} should use \type{\wordright} if its argument is narrower than \type{\hsize}, or make a right-aligned paragraph with it when it's wider. Below, \type{\wordorparagraphright} is tested with a short text, that has enough room on the same line. \blank Reference: \input ward\wordright{same line, right} \blank Implementation as a grouped command (it doesn't work): \input ward\groupedwordorparagraphright{same line, right} \blank Normal implementation, not as a grouped command (it works): \input ward\wordorparagraphright{same line, right} \stoptext ---------------------------------------------------- Unfortunately the grouped version is the one I need, because it's used in a register, and it would give an error if not defined through \groupedcommand: \setupregister[myregister] [pageleft=\wordorparagraphright\bgroup,pageright=\egroup] TIA, Massi

2 3

special chapter label
by jbf 02 Sep '20

02 Sep '20

Am working on a book where most chapters are simply labeled Chapter One, Chapter Two etc., and this has been achieved easily enough with \setuplabeltext[chapter=Chapter ] (also including \setupheads[conversion=Words] to get One, Two instead of 1 2). But several chapter labels need to have a date range after them, e.g. *Chapter Three: 1820-1880*. I have tried introducing a new \setuplabeltext[chapter=Chapter: 1820-1880 ] just before the \startchapter command, but this results in*:** * *Chapter: 1820-1880 Three* (and I also hope that introducing this does not also affect Chapter Four since that will have a different set of dates). How can I get a specific labeltext set up so that the result is *Chapter Three: 1820-1880*, and also ensure that other chapters either return to just the chapter number or, if needs be, can also indicate different date ranges? I have looked everywhere on the wiki for ideas to help me, but so far no luck. Julian

2 1

defining font family for several options
by jbf 01 Sep '20

01 Sep '20

Perhaps someone can assist me with the following query. I have a situation where I need to use more than one sans serif fonts (especially within complicated chapter heads). I currently have the following: \definefontfamily [mainface] [rm] [alegreya] \definefontfamily [mainface] [ss] [dax][tf=file:dax-regular] \definefontfamily [mainface] [mm] [alegreya] \setupbodyfont[mainface] \setupbodyfont[11pt] But what if I need to have, in addition to the Dax sans serif typeface, an additional sans serif typeface such as ITCAvantGarde? How do I declare that? Do I just give it another name, e.g. \definefontfamily[chapter][itcavantgarde] etc? If I did that, how then do I refer to it? Obviously not just as {\ss my text} since that would call in the dax font. Julian

4 5

Error with negative superscript
by Jan Willem Flamma 01 Sep '20

01 Sep '20

2 1

new upload
by Hans Hagen 01 Sep '20

01 Sep '20

Hi, In order to keep the 'context is good for toy math' reputation up to date, in lmtx we can now have proper discretionaries in math and math in discretionaries. The kind of things no one asks for but they might be useful in educational settings. Here are some examples (): \starttext \showframe \enabletrackers[math.toysymbol] \definemathtoysymbol[Plus] [bin][+] \definemathtoysymbol[Minus][bin][-] \definemathtoysymbol[Equal][rel][=] $\dorecurse{199} { x_{#1} \ifodd#1\relax\Plus\else\Minus\fi } x_{200} \Equal n$ \blank \dorecurse{10} { test \discretionary {\darkred hel $\sqrt{y}$ lo} {\darkgreen good $\sqrt{z}$ bye} {\darkblue wel $\sqrt{x}$ come} test } \blank \dorecurse{10} {test me #1 $x + 2x \discretionary class 2 {$+ \, \cdots $} {$ \cdots \, +$} {$+ \, \cdots \, +$} nx$ test } \stoptext You might be able to guess from this code what is supposed to happen. I'll play a bit more with this later (assuming that it's somehow useful). We could predefine a bunch. As usual there might be issues but I'll sort them out when we run into them (it's a non critical feature with not much impact). Hans (who must not forget to document it somewhere) ----------------------------------------------------------------- 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 2

own answer to part of the question re typeface options
by jbf 01 Sep '20

01 Sep '20

I have come up with part answers to my two questions. The remaining unanswered question is in the final line. The question I can now answer, after some experimenting, is how to ensure that I can use small caps as part of the Alegreya family when I need to do so. This is how my definitions now look (the solutions are highlighted): \definefontfamily [mainface] [rm] [alegreya] *[sc=file:alegreyasc-bold]* \definefontfamily [mainface] [ss] [dax][tf=file:dax-regular] \definefontfamily [mainface] [mm] [alegreya] \setupbodyfont[mainface] This now enables me to do: {\sc text in small caps} and the rest of the paragraph as normal (alegreya-regular)... I also now know, using the same type of solution above, that I can use two different weights of Dax, as follows: \definefontfamily [mainface] [ss] [dax][tf=file:dax-regular,*bf=file:dax-medium*] which enables me to do as follows: {\ss\bf My subheading} and it will be in Dax-medium font. But I also want to be able to use a second sans serif font, namely ITCAvantGardePro-Md. Can I have two 'mainface' definitions for [ss]? Or how would I achieve this? Julian

1 0

Verbatim typing and compound breakpoints
by Christoph Reller 01 Sep '20

01 Sep '20

Dear List, I am using ConTeXt LMTX 2020.08.28 13:58 with the following M(N)WE: \definetype[typeLUA][option=LUA] \setbreakpoints[compound] \starttext \typeLUA{function(argument)} \stoptext Sadly, it does not compile. The problem seems to be the simultaneous use of compound breakpoints and parenthesis. The error message is: callback error: ...est/tex/texmf-context/tex/context/base/mkiv/lang-ini.lua:509: bad argument #1 to 'prehyphenchar' (luatex.lang expected, got no value) stack traceback: [C]: in function 'lang.prehyphenchar' ...est/tex/texmf-context/tex/context/base/mkiv/lang-ini.lua:509: in field 'prehyphenchar' ...est/tex/texmf-context/tex/context/base/mkiv/typo-brk.lua:171: in local 'method' ...est/tex/texmf-context/tex/context/base/mkiv/typo-brk.lua:392: in upvalue 'typesetters_breakpoints_handler' [string "local tonut = nodes.tonut..."]:16: in function <[string "local tonut = nodes.tonut..."]:11> (...tail calls...) ...est/tex/texmf-context/tex/context/base/mkiv/node-pro.lua:88: in function <...est/tex/texmf-context/tex/context/base/mkiv/node-pro.lua:79> How can I prevent this? Is this a bug? Cheers, Christoph

1 1