- ntg-context - NTG Mailing Lists

Strange behavior of a macro
by Fabrice Couvreur 16 Aug '21

16 Aug '21

Hello, I don't understand why this macro works with this simple example but return the following error if I use it for chapters in my book. Thanks Fabrice %%%% \setupbodyfont [newcomputermodern-book,11pt] \unexpanded\def\N{\math{\mathbb{N}}\autoinsertnextspace} \defineenumeration [test] [title=yes, text={Test}, style=italic] \starttext \N \starttest \m{\forall n \in \N} \stoptest \stoptext %%%% tex error > tex error on line 64 in file ./terminale_suites_2.tex: Use of \N doesn't match its definition <line 3.64> Soient \u, \v deux suites définies sur \N, \m{l} et \m{l'} deux réels. 54 \startitem 55 \u converge vers \m{l}, 56 \stopitem 57 \stopitemize 58 alors \m{l\geqslant 0}. 59 \stopproposition 60 \startremarque 61 Nous retiendrons que le passage à la limite sur une inégalité stricte restitue une inégalité large. 62 \stopremarque 63 \startcorollaire 64 >> Soient \u, \v deux suites définies sur \N, \m{l} et \m{l'} deux réels. 65 66 Si 67 68 \startitemize 69 \startitem 70 les suites \u et \v convergent respectivement vers \m{l} et \m{l'}, 71 \stopitem 72 \startitem 73 \m{\forall n \in\mathbb{N}, \thinspace u_n>v_n}, 74 \stopitem If you say, e.g., '\def\a1{...}', then you must always put '1' after '\a', since control sequence names are made up of letters only. The macro here has not been followed by the required stuff, so I'm ignoring it. mtx-context | fatal error: return code: 256 %%%%

2 1

result saved in file: ./file.pdf
by Peter Münster 16 Aug '21

16 Aug '21

Hi, The latest version of ConTeXt writes "result saved in file: ./file.pdf" instead of "saved in file: file.pdf", that breaks the error-checker of AucTeX. Is this wanted? Or are you going to change it back to a filename without the "./"? TIA, -- Peter

2 3

'--noconsole' or '--batchmode` still logs to console? | 1.04 Aug-10 version
by Ramkumar KB 16 Aug '21

16 Aug '21

Hi, I noticed that (in the latest version) that context command with '--batchmode' or '--noconsole` still logs to the console? Not sure if this is a regression issue. I am using the 1.04 Aug-10 version. best regards, Ramkumar

1 0

Progressively encouraging page/column breaks at \blank with penalties
by Joey McCollum 15 Aug '21

15 Aug '21

Hi, I'm trying to implement a section break marker in a grid layout. At a section break, two lines of space should separate the subsequent segments of text (just plain paragraphs, in this case), and a symbol (in the example below, "X") should be set in the middle of these two lines. For my purposes, the section break symbol should never occur at the top of a page or column, and it is more desirable to have a page or column end with the section break symbol than to have a single orphaned line follow the symbol at the end of the page or column. Based on these constraints, I thought that using the "samepage" and "preference" options for the first and second line breaks would work nicely: ``` \define\SectionBreak{% \blank[halfline, samepage]% non-breaking to ensure that no column begins with the section break symbol \startalignment[middle]% {X}% section break symbol \stopalignment% \blank[halfline, preference]% this can (and, if possible, should) be broken across a column ``` This does successfully prevent the placement of the symbol at the top of a page/column, but it doesn't encourage the placement of the symbol at the end of a page/column as often as I would like. I tried replacing the "preference" option with options with better negative penalties, like "penalty:-1000", "penalty:-2000", and even "penalty:-5000", but these didn't make any difference. The option "penalty:-10000" trivially works, but it forces a page/column break at every section break marker, which is far too extreme. Is this normal behavior? I would have thought that progressively more negative penalties would gradually encourage page/column breaks, but this doesn't seem to happen. In the following MWE, the "preference" and "penalty" options (apart from "penalty:-10000") for the second line break don't change the total page count or appearance of the final page at all (which would be expected in a document of this size): ``` \setuplayout[ grid=yes %enable baseline grid ] \setupinterlinespace[18bp] % text line spacing %Define macro for section break: \define\SectionBreak{% \blank[halfline, samepage]%non-breaking to ensure that no column begins with the section break symbol \startalignment[middle]% {X}% section break symbol \stopalignment% \blank[halfline]% a column break here is neither encouraged nor discouraged % \blank[halfline, preference]% this should encourage a column break here, but it doesn't seem to make a difference % \blank[halfline, penalty:-1000]% still no difference % \blank[halfline, penalty:-2000]% still no difference % \blank[halfline, penalty:-5000]% still no difference % \blank[halfline, penalty:-10000]% this works, but it is too extreme! } %Set things up for fakewords: \usemodule[visual] \setupsystem[random=10] \starttext \dorecurse{400}{\fakewords{20}{100}\SectionBreak} \stoptext ``` As always, any help is appreciated! Joey

2 2

Failure when loading variable font
by Marcel Krüger 15 Aug '21

15 Aug '21

Hi, the latest ConTeXt version fails for the following document: \definefontfeature [default:test] [default] [axis={Weight=100}] \definefont [SomeFont] [file:Fraunces.ttf*default:test] \starttext \SomeFont Abcdef \stoptext and the font from https://github.com/undercasetype/Fraunces/raw/master/fonts/Fraunces%5BSOFT%… renamed to Fraunces.ttf with the error message otf reader > user instance: weight=100, factors: 0 -1.0 0 0 otf reader > fatal error in file 'Fraunces.ttf': ...e0dde776fb1556f32e/formats/luametatex/font-ttf-macro.lua:274: attempt to index a nil value (local 'p1') stack traceback: ...e0dde776fb1556f32e/formats/luametatex/font-otr-macro.lua:2339: in metamethod 'index' ...e0dde776fb1556f32e/formats/luametatex/font-ttf-macro.lua:274: in upvalue 'applyaxis' ...e0dde776fb1556f32e/formats/luametatex/font-ttf-macro.lua:1428: in field 'gvar' ...e0dde776fb1556f32e/formats/luametatex/font-ttf-macro.lua:1155: in local 'reader' ...e0dde776fb1556f32e/formats/luametatex/font-otr-macro.lua:2084: in upvalue 'readtable' ...e0dde776fb1556f32e/formats/luametatex/font-otr-macro.lua:2197: in upvalue 'readdata' ...e0dde776fb1556f32e/formats/luametatex/font-otr-macro.lua:2252: in function <...e0dde776fb1556f32e/formats/luametatex/font-otr-macro.lua:2235> [C]: in function 'xpcall' ...e0dde776fb1556f32e/formats/luametatex/font-otr-macro.lua:2341: in upvalue 'loadfont' ...e0dde776fb1556f32e/formats/luametatex/font-otr-macro.lua:2396: in field 'loadfont' ...mtx/tex/texmf-context/tex/context/base/mkiv/font-otl.lua:160: in field 'load' ...mtx/tex/texmf-context/tex/context/base/mkiv/font-otl.lua:599: in upvalue 'otftotfm' ...mtx/tex/texmf-context/tex/context/base/mkiv/font-otl.lua:627: in function <...mtx/tex/texmf-context/tex/context/base/mkiv/font-otl.lua:626> (...tail calls...) ...mtx/tex/texmf-context/tex/context/base/mkxl/font-def.lmt:377: in function <...mtx/tex/texmf-context/tex/context/base/mkxl/font-def.lmt:365> (...tail calls...) ...mtx/tex/texmf-context/tex/context/base/mkxl/font-def.lmt:483: in field 'read' ...mtx/tex/texmf-context/tex/context/base/mkxl/font-ctx.lmt:1336: in function <...mtx/tex/texmf-context/tex/context/base/mkxl/font-ctx.lmt:1193> (...tail calls...) fonts > otf loading > loading failed due to read error (This run used luametatex, but the same issue occurs when using luatex) The same font worked correctly with the ConTeXt version from 2021-05-20. Best regards, Marcel

3 2

Re: [NTG-context] new upload/issue with t-vim?
by Benjamin Buchmuller 13 Aug '21

13 Aug '21

I'm not sure if it's related to this latest: ConTeXt ver: 2021.08.07 22:53 LMTX fmt: 2021.8.8 int: english/english or a previous one, but with this one: ConTeXt ver: 2021.07.30 00:57 LMTX fmt: 2021.8.8 int: english/english My document compiled fine. When I use the t-vim module (freshly installed again from the garden; but I also tried to replace some files from the GitHub, but not sure if I did it right …), I now get an error when I do something like \usemodule[vim] \definevimtyping[vimR] \typevimRfile{path_to_file.R} % specifically: {../sourcecodes/myfile.R} -- lua error > lua error on line 2 in file virtual://block.sourcecode.7: token call, execute: ...ConTeXt/tex/texmf-context/tex/context/base/mkiv/l-io.lua:70: bad argument #1 to '?' (string expected, got nil) stack traceback: [C]: in ? (...tail calls...) ...ConTeXt/tex/texmf-context/tex/context/base/mkiv/l-io.lua:70: in function 'io.loaddata' ...onTeXt/tex/texmf-context/tex/context/base/mkiv/l-md5.lua:91: in upvalue 'checksum' ...eXt/tex/texmf-context/tex/context/base/mkiv/grph-fil.lua:97: in field 'run' [ctxlua]:1: in main chunk <empty file> -- Any clues? For the moment, I switched back to the older version as I have to get some work finished, which is why I can't dig deeper at the moment. If a MWE would help, I'll try to make one later this week. Thanks Benjamin

3 4

Both pdfinfo & exiftool have trouble with 1.0.4 but works with 1.0.3
by Ramkumar KB 13 Aug '21

13 Aug '21

Hi, We use PDF tools like mutool, pdfinfo (from poppler) and exiftool in our workflow (once the PDFs are created by ConTeXt). But looks like we have hit upon some regression issue between 1.0.3 and 1.0.4 versions. Both pdfinfo (from poppler) and exiftool are able to read PDFs created from 1.0.3 but have trouble reading PDFs created with 1.0.4. Please see below logs for details. Our 1.0.4 is from April-2021. We will try to upgrade to the latest 1.0.4 and try again. mtx-context | ConTeXt Process Management 1.04 mtx-context | mtx-context | main context file: /ConTeXt/apr2021/tex/texmf-context/tex/context/base/mkiv/context.mkiv mtx-context | current version: 2021.04.21 11:39 mtx-context | main context file: /ConTeXt/apr2021/tex/texmf-context/tex/context/base/mkxl/context.mkxl mtx-context | current version: 2021.04.21 11:39 mtx-context | ConTeXt Process Management 1.03 mtx-context | mtx-context | main context file: /ConTeXt/sep2020/tex/texmf-context/tex/context/base/mkiv/context.mkiv mtx-context | current version: 2020.09.20 23:02 mtx-context | main context file: /ConTeXt/sep2020/tex/texmf-context/tex/context/base/mkiv/context.mkxl mtx-context | current version: 2020.09.20 23:02 *====pdfinfo (from Poppler)====* ~/TeX$ pdfinfo Hello-world_1.0.4.pdf Syntax Error: Missing 'endstream' or incorrect stream length Syntax Error: Missing 'endstream' or incorrect stream length Title: Hello world! Subject: A ConTeXt template Keywords: template Author: Mickey Mouse Creator: LuaMetaTeX 2.09 20210418 + ConTeXt LMTX 2021.04.21 11:39 Producer: LuaMetaTeX-2.09 CreationDate: Tue Aug 10 10:18:36 2021 +08 ModDate: Tue Aug 10 10:18:36 2021 +08 Tagged: no UserProperties: no Suspects: no Form: none JavaScript: no Pages: 2 Encrypted: no Page size: 612 x 792 pts (letter) Page rot: 0 File size: 39062 bytes Optimized: no PDF version: 1.7 ~/TeX$ pdfinfo Hello-world_1.0.3.pdf Title: Hello world! Subject: A ConTeXt template Keywords: template Author: Mickey Mouse Creator: LuaTeX 2.07 20200920 + ConTeXt MkIV 2020.09.20 23:02 Producer: LuaTeX-2.07 CreationDate: Tue Aug 10 09:16:30 2021 +08 ModDate: Tue Aug 10 09:16:30 2021 +08 Tagged: no UserProperties: no Suspects: no Form: none JavaScript: no Pages: 2 Encrypted: no Page size: 612 x 792 pts (letter) Page rot: 0 File size: 39861 bytes Optimized: no PDF version: 1.7 *====exiftool====* ~/exiftool/Image-ExifTool-12.29/exiftool Hello-world_1.0.4.pdf ExifTool Version Number : 12.29 File Name : Hello-world_1.0.4.pdf Directory : . File Size : 38 KiB File Modification Date/Time : 2021:08:10 10:19:52+08:00 File Access Date/Time : 2021:08:10 10:20:17+08:00 File Inode Change Date/Time : 2021:08:10 10:19:52+08:00 File Permissions : -rwxr-x--- File Type : PDF File Type Extension : pdf MIME Type : application/pdf PDF Version : 1.7 Linearized : No Warning : Error reading stream data ~/exiftool/Image-ExifTool-12.29/exiftool Hello-world_1.0.3.pdf ExifTool Version Number : 12.29 File Name : Hello-world_1.0.3.pdf Directory : . File Size : 39 KiB File Modification Date/Time : 2021:08:10 09:17:51+08:00 File Access Date/Time : 2021:08:10 09:18:00+08:00 File Inode Change Date/Time : 2021:08:10 09:17:51+08:00 File Permissions : -rwxr-x--- File Type : PDF File Type Extension : pdf MIME Type : application/pdf Linearized : No Author : Mickey Mouse Con Te Xt Jobname : Hello-world Con Te Xt LMTX : 0.10 Con Te Xt Support : contextgarden.net Con Te Xt Time : 2021-08-10 09:16 Con Te Xt Url : www.pragma-ade.com Con Te Xt Version : 2020.09.20 23:02 Create Date : 2021:08:10 09:16:30+08:00 ID : Hello-world | 2021-08-10T09:16:30+08:00 Keywords : template Modify Date : 2021:08:10 09:16:30+08:00 Subject : A ConTeXt template Te X Support : tug.org Language : en Format : application/pdf Creator : Mickey Mouse Description : A ConTeXt template Title : Hello world! Id : Hello-world | 2021-08-10T09:16:30+08:00 Con Te Xt Jobname : Hello-world Con Te Xt Time : 2021:08:10 09:16 Con Te Xt Url : www.pragma-ade.com Con Te Xt Support : contextgarden.net Con Te Xt Version : 2020.09.20 23:02 Con Te Xt LMTX : 0.10 Te X Support : tug.org Lua Te X Version : 2.07 Lua Te X Functionality : 20200920 Lua Te X Lua Version : 5.4 Lua Te X Platform : win64 Creator Tool : LuaTeX 2.07 20200920 + ConTeXt MkIV 2020.09.20 23:02 Metadata Date : 2021:08:10 09:16:30+08:00 Producer : LuaTeX-2.07 Trapped : False Document ID : uuid:41a746a2-4d66-ad14-387a-ace654b14d2c Instance ID : uuid:125a13c6-4cf4-9bff-2617-972e13516712 Page Mode : UseNone Page Count : 2 PDF Version : 1.7

2 3

15th International ConTeXt Meeting (registration closes Aug 22)
by Taco Hoekwater 13 Aug '21

13 Aug '21

Hi all, There is still room for some extra participants for the ConTeXt meeting in Bassenge, Belgium from Sept 20 to Sept 25. Despite the still somewhat lingering situation wrt COVID-19, we are now certain that the meeting can and will in fact take place in person. Hurrah! Even if we still have room by then, registration will close on Aug 22, because by that time we need to make final arrangements for T-shirt printing and catering. So if you are still on the fence about attending, do not wait too long! Also remember that it is possible for ConTeXt Group members to attend online-only for free. That is less than ideal because you cannot join us for a drink and a chat, but it gives you bragging rights for attending, and you will get a T-shirt as well ! (if you register before Aug 22) You can easily become a member of CG by filling in the form at https://group.contextgarden.net/register.shtml Besides being able to register for the online portion of the upcoming meeting, you will also receive the nicely printed ConTeXt journal, and additionally you will help the ConTeXt Group to do more for the community in the future. Even if you are not going to attend the online meeting, we think becoming a CG member is a great idea! More that fifty people have joined already! To see more details about the upcoming meeting, see the website at https://meeting.contextgarden.net/ In other news, there is now a provisional programme page: https://meeting.contextgarden.net/2021/programme.shtml I can't wait to see (some of) you in person in Bassenge! Best wishes, Taco — Taco Hoekwater E: taco(a)bittext.nl genderfluid (all pronouns)

1 0

Footnotes in columns
by Clyde Johnston 13 Aug '21

13 Aug '21

I can no longer print the footnotes when I using columns in LTMX. If I remove the \{start|stop}columns, it works fine. This works on my old MKIV 2018.07.02 14:39 version. \setupcolumns[n=2,rule=off,balance=no] \starttext \startcolumns \input ward\footnote{A small footnote here} \stopcolumns \stoptext Context Version: 2021.01.24 16:07 Clyde

4 8

Conditional formatting with *frontpart, *bodypart, *backpart modes
by Joey McCollum 12 Aug '21

12 Aug '21

Hi, I was curious about the possibility of handling general formatting settings (e.g., page layout, headers and footers, page numbering, alignment, default body font assignment, etc.) conditionally for front, body, and back matter using modes. According to the wiki page at https://wiki.contextgarden.net/Modes, this should be doable with blocks like \startmode[*frontpart] ... \stopmode, but even in the following minimal example, the conditional formatting isn't getting applied: ``` \startmode[*frontpart] \setupbodyfont[modern, 12pt] \stopmode \startmode[*bodypart] \setupbodyfont[pagella, 12pt] \stopmode \startmode[*backpart] \setupbodyfont[termes, 12pt] \stopmode \starttext \startfrontmatter \input knuth\par \stopfrontmatter \startbodymatter \input knuth\par \stopbodymatter \startbackmatter \input knuth\par \stopbackmatter \stoptext ``` Is there something obvious that I'm missing? Or is there a different recommended approach to conditional formatting by front/body/back matter division? Thank you! Joey

2 1