July 2021 - ntg-context - NTG Mailing Lists

Re: [NTG-context] Use of lettrine module in LMTX
by Wolfgang Schuster 25 Jul '21

25 Jul '21

Gerben Wierda schrieb am 22.07.2021 um 08:43: > So, basically, the page on ConTeXt garden about using older modules in > LMTX is incomplete: not all modules actually work. Many of the modules on the garden are 10 years and older and predate MkIV/LuaTeX. A lot has changed since then and LMTX added many new commands which replaced older mechanism. There is no way all modules can work after these changes (especially modules which add font support in MkII). Wolfgang

6 5

Testing for LMTX: \ifmode
by Axel Kielhorn 25 Jul '21

25 Jul '21

Hi, I have a document that doesn’t work with LMTX right now. While testing LMTX I would like to exclude certain passages and work on them later. When I run the following: \doifmode{*mkiv}{mkiv} \doifmode{*contextlmtxmode}{contextlmtx} \doifmode{*lmtx}{lmtx} I always get „mkiv“. I’ve tried - pre LMTX context - LMTX --luatex - LMTX (2021.07.23) What is the recommended way to detect LMTX? Greetings Axel

3 3

\setupinitial: style Parameter resets size
by Axel Kielhorn 25 Jul '21

25 Jul '21

Hi, since the lettrine module does not work with LMTX, I’ve looked into \setupinitial. (There is a different thread about this.) There is a „style“ parameter to change the style, but whenever I change the style, the font size is reset. This is not what I expected. This was the case in context before LMTX, thus it is not a regression. % !TEX TS-program = ConTeXt (LuaTeX LMTX2021) % !TEX encoding = UTF-8 Unicode \starttext \setupinitial[color=red] \start \setupinitial[n=2,m=1] \placeinitial\input ward \stop \start \setupinitial[style=\tf,n=2,m=1] \placeinitial\input ward \stop \start \setupinitial[font=Roman at 32 pt,n=2,m=1] \placeinitial\input ward \stop \start \setupinitial[style=\it,n=2,m=1] \placeinitial\input ward \stop \start \setupinitial[font=Italic at 32 pt,n=2,m=1] \placeinitial\input ward \stop \start \setupinitial[style=\it,font=Italic at 32 pt,n=2,m=1] \placeinitial\input ward \stop \stoptext Are my expectations wrong? Greetings Axel

1 0

weekend update
by Hans Hagen 25 Jul '21

25 Jul '21

Hi, This time the update has, appart from already mentioned mp fixes and additions, another new feature. % runpath=texruns:whatever % runpath=e:/temporary/texruns/runtest % runpath=temp:texruns/runtest % runpath=home:texruns/runtest \starttext test \stoptext In context the first line can be used to control some aspects of the run and runpath (also as command line switch) will process the document elsewhere. The main reason for this feature is that when you have files in for instance a git repository (or export), you don't want the run path to be polluted by temporary files because everything can end up in the repository when it gets updates (after all these years I don't expect this pollution issue to be solved; svn is more explicit in what goes in). So, for instance the manuals are on clean paths (on my machine i (am) put(ting) experiments, todo's etc under an ignored /private subpath which means that styles can still be found if needed). The texruns: prefix resolves to an environment variable with the same name or when not set, to the temp directory. The temp: and home: prefixes resolve (as usual) to their counterparts (prefixes are a very old mkii mechanism but still useful). When not present a path will be created, when no chdir is possible the run aborts. There are probably some cases when resources are not found but that will be dealt with in due time. I might also update the underlying mechanisms at some point. I already adapted some manuals so that means that when users process these themselves they will not see the runfiles fly to the temp path unless 'texruns' is configured. So be it. 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

Call for papers: CG journal 2020
by Henning Hraban Ramm 24 Jul '21

24 Jul '21

Hi, do you remember our ConTeXt meeting 2020 in Sibřina? (programme attached) There were some interesting talks and presentations that should get preserved in our current journal (to be distributed at the meeting in Bassenge this fall). Also, additional articles are always welcome – there were a lot of interesting new features and solutions since then. So far, I/we got only one(!) article, by Taco on MetaPost. Please don’t let me/us down and hand in your articles until end of July (but ASAP)! @Harald: Please send the latest version of your German report, too! I’ll translate it into ConTeXt. Thank you – I’m looking forward to another interesting issue of CG journal! Yours, Hraban

1 2

question about followingup.pdf
by Pablo Rodriguez 24 Jul '21

24 Jul '21

Hi Hans, current latest has content added to the Following Up manual and also to the LMTX manual. In latest, the PDF document for LMTX is from yesterday, but the PDF for the Following Up manual is almost two years old. Is this intended or am I missing something? Many thanks for your help, Pablo -- http://www.ousia.tk

2 3

Percentage stacked bars chart
by Jorge Manuel 24 Jul '21

24 Jul '21

Dear Sirs, Is there a way (out of the box) to draw percentage stacked bars chart with metapost or MetaFun xl? Thanks for your time and support. Jorge Magalhães

3 6

lmt_chart_bar with data from luacode
by Jorge Manuel 24 Jul '21

24 Jul '21

Dear Sirs If I tried: \starttext \startluacode sample = {10,30,30,40} function MP.GetP() mp.print(sample) end \stopluacode \startMPcode draw lmt_chart_bar [ width = 8cm, height = 10mm, samples = {lua.MP.GetP()} , trace = true, maximum = 100, linewidth = 1mm, showlabels = false, originsize = 0, labelanchor = "lft", labelcolor = "black" labelstyle = "bfxx" legendstyle = "tfxx", labelstrut = "yes", ] ; \stopMPcode \stoptext This works. But with an extra element in the sample table: \starttext \startluacode sample = {10,30,30,40,50} function MP.GetP() mp.print(sample) end \stopluacode \startMPcode draw lmt_chart_bar [ width = 8cm, height = 10mm, samples = {lua.MP.GetP()} , trace = true, maximum = 100, linewidth = 1mm, showlabels = false, originsize = 0, labelanchor = "lft", labelcolor = "black" labelstyle = "bfxx" legendstyle = "tfxx", labelstrut = "yes", ] ; \stopMPcode \stoptext Don't works anymore. Why? Thanks for your time and support. Sent with a Spark

3 4

Every odd row with a background color with extreme tables?
by T. Kurt Bond 23 Jul '21

23 Jul '21

With natural tables I can define a color, tell the table to have to use color backgrounds and turn the frame off and get every odd row in all my tables will have that color for the background. ========== Example ============================================================ \definecolor[grayback][r=.8,g=.8,b=.8] \setupTABLE[background=color,frame=off] \setupTABLE[row][odd][backgroundcolor=grayback] ========== End of Example ===================================================== Can I get this same effect with extreme tables? My first try with extreme tables looked like this: ========== Example ============================================================ \definecolor[tablebackground][r=.8,g=.8,b=.8] \setupxtable[background=color,frame=off] \setupxtable[row][odd][backgroundcolor=tablebackground] ========== End of Example ===================================================== That didn't seem to have any effect. Is there a way to have every odd row of every table in my document have color background? -- T. Kurt Bond, tkurtbond(a)gmail.com, tkurtbond.github.io and tkb.tx0.org

3 3

LMTX: some alignment issues
by Gerben Wierda 23 Jul '21

23 Jul '21

[still working to somewhat reproduce my old mkii setup in LMTX] The following is a minimal example that shows the following: context test2.tex results in The first line after the initials not as much indented as it should be Character protrusion in a footnote does not work (see “refer-“ at the end of the 5th line of the footnote) (I understand the trouble on the first line context --mode=OPTIMA test2.tex results in The first line after the initials not as much indented as it should be "because” is not hyphenated. Note, I see this is a smaller font setup where there is clearly an option to hyphenate, the minimum example shows the same effect, but potentially not from the same cause) Character protrusion in a footnote does not work context --mode=OPTIMANOVA test2.tex results in The first line after the initials not as much indented as it should be Multiple instances of extending beyond the right Character protrusion in a footnote does not work Adding \setupalign[hanging,hz] to the Optima Nova example results in ‘because’ on the first line to be hyphenated as ‘be-cause’ and pigeonhole in a later line as 'pi-geonhole'. I am adding a screen shot of part of the Optima Nova result as most will not have that font available: - All show no protrusion in the footnotes - All show a problem with the first line after the initial - When using Optima Nova, hyphenation isn’t used while the situation in Optima looks nearly identical. MVP source: %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% \definepapersize[smallpaperback][width=5in,height=8in] \setuppapersize[smallpaperback][smallpaperback] \setuplayout[location=doublesided] \setuppagenumbering[alternative=doublesided] \setupsectionblock[frontpart][page=no] \setupsectionblock[bodypart][page=no] \setupsectionblock[appendix][page=no] \setupsectionblock[backpart][page=no] \definefontfeature [default] [default] [protrusion=quality,expansion=quality] \setupbodyfont[default,11pt] \startmode[OPTIMANOVA] \definefontfamily [bookfont] [ss] [Optima nova LT Pro] [tf=style:Regular, bf=style:Medium, it=style:Italic, bi=style:Medium Italic] \setupbodyfont[bookfont,11pt] \stopmode \startmode[OPTIMA] \definefontfamily [bookfont] [ss] [Optima] [tf=style:Regular, bf=style:Bold, it=style:Italic, bi=style:Bold Italic] \setupbodyfont[bookfont,11pt] \stopmode \setupalign[hanging] % only protrusion \showframe \starttext \setupindenting[next] \placeinitial \input tufte Test footnote\footnote{If you are not technical and terms like `application server', `caught exceptions', or `web proxy' in the fragment that follows, do not immediately get you started, do not worry: there is no need to know what I am talking about here in a technical sense. You can read this without understanding any of the technical references. Just skip over them, their specifics are not important to the story. They are real enough, though. You can trust me on that, or ask your engineers.} \stoptext %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% Gerben Wierda (LinkedIn <https://www.linkedin.com/in/gerbenwierda>) R&A Enterprise Architecture <https://ea.rna.nl/> (main site) Book: Chess and the Art of Enterprise Architecture <https://ea.rna.nl/the-book/> Book: Mastering ArchiMate <https://ea.rna.nl/the-book-edition-iii/>

1 0