July 2020 - ntg-context - NTG Mailing Lists

\type ignores space between command and bracket
by Wolfgang Schuster 02 Feb '24

02 Feb '24

Hi, in the following code example the result from \type lacks the space between \cmd and the following left bracket. \starttext \starttyping \cmd [...] \stoptyping \type{\cmd [...]} \stoptext Wolfgang

3 2

Luatex 1.12.0 announcement.
by luigi scarso 27 May '23

27 May '23

============================================================== LuaTeX 1.12.0 2020-03-15 ============================================================== This is the release for TeX live 2020. --shell-restricted now forbids loading of dso (dll/so object) Scaled virtual font Aadditional primitives \eTeXglue[stretch|shrink]order for querying order the etex way. Extra features runtoks tex.getmodenames() (as these can differ per engine/version) Permit nested runtoks in more complex situations of nesting (HH) More accurate and correct test for tex.[set|get]math Minor clean-up and bugs fixed -- luigi

1 4

Laundry symbols (now: altered picture)
by Procházka Lukáš Ing. - Pontex s. r. o. 02 Jan '22

02 Jan '22

Hello ConTeXters, is there a way how to get laundry symbols into ConTeXt? - The image is copied from "The Comprehensive LATEX Symbol List", Scott Pakin. TIA. Best regards, Lukas -- Ing. Lukáš Procházka [mailto:LPr@pontex.cz] Pontex s. r. o. [mailto:pontex@pontex.cz] [http://www.pontex.cz] Bezová 1658 147 14 Praha 4 Tel: +420 244 062 238 Fax: +420 244 461 038

5 10

Unicode normalization and Hebrew in ConTeXt
by Joey McCollum 18 Aug '21

18 Aug '21

I am typesetting a document in Hebrew that includes pointing (e.g., vowels, shin and sin dots, dagesh, etc.) using ConTeXt. The Hebrew text that I want to typeset has been normalized into Unicode's NFC canonical form. It is well-known that the Unicode canonical ordering of Hebrew points conflicts with the recommended mark ordering of specific points based on their functions (see https://www.sbl-site.org/Fonts/SBLHebrewUserManual1.5x.pdf for more on this topic). Thankfully, many typesetting engines automatically reorder the points to ensure that they are combined according to the specifications of many fonts. I'm pretty sure that XeLaTeX is one of these, as it typesets Hebrew letters with multiple points correctly even when the Hebrew text is in NFC form. My question is, can ConTeXt with LuaTeX handle the same situation correctly? In the following minimal example, ConTeXt typesets pointed Hebrew correctly when the characters are in the typographically recommended order, but not when they are in Unicode canonical order: ``` %Setup Hebrew text font: \definefontfeature[f:pointedhebrew][default][ ccmp=yes, mark=yes, script=hebr ] \definefontfamily[hebrew] [rm] [SBL Hebrew] [features=f:pointedhebrew] %Set the body font: \setupbodyfont[hebrew] %Set up right-to-left alignment: \setupalign[r2l] \starttext %Characters after normalization, in Unicode canonical order (bet + segol + dagesh + final nun): בֶּן %A word with characters in typographically recommended order (bet + dagesh + segol + final nun): בֶּן \stoptext ``` I typeset this using ConTeXt version 2020.03.10, as released with TeXLive 2020. I got the SBL Hebrew font from https://www.sbl-site.org/educational/BiblicalFonts_SBLHebrew.aspx. According to the font's user manual (see the link above the MWE), the font should be able to combine the marks to form the correct glyph regardless of their order after the consonant, but that doesn't seem to be the case here. I also tried using the predefined "hebrew" featureset, but that did not change anything. Is there some other OpenType feature or featureset I need to enable to fix this, or is there some module or option I can include to get ConTeXt to typeset Unicode-normalized Hebrew as if it were ordered in the recommended way, like XeLaTeX does? I see that the uninormalize module is mentioned in the thread "XeLaTeX, LuaLaTeX, fontspec, unicode and normalization" on TeX Stack Exchange ( https://tex.stackexchange.com/questions/229044/xelatex-lualatex-fontspec-un…) can that be used with ConTeXt? Thank you, Joey

2 10

img.scan in lmtx?
by Henning Hraban Ramm 05 Aug '21

05 Aug '21

Hi, I use the lua function img.scan{filename}, but in lmtx I get "attempt to index a nil value (global 'img')", so I guess this got renamed or moved? HR

2 6

LMTX: different output if dots are used in the file name
by Marco Patzer 09 Jul '21

09 Jul '21

Hi! LMTX and MkIV behave differently if dots are used in the file name. Example: printf '%s\n' '\starttext\null\stoptext' > foo.10.tex && context foo.10.tex MkIV: → foo.10.pdf LMTX: → foo.pdf Is this intentional? This is LuaMetaTeX, Version 2.06.05 current version: 2020.05.25 23:39 Marco

5 17

Re: [NTG-context] Installing VSCode extension?
by Jeong Dal 17 Dec '20

17 Dec '20

Dear Alasdair McAndrew, I am using vscode in iMac, so my setting may not work for you. 1. First, find files for vscode in your TeX folder. In my case, /ConTeXt-homefolder/tex/texmf-context/context/data/vacode/extensions/context/*.* 2. In a homefolder, there is a hidden folder “.vacode”. Copy context/*.* to ./vscode/extensions/context/*.* 3. Open vscode and enable context-extension. Since it was long time ago, my memory may not be correct. However, I hope that it may give you an idea. Best wishes, Dalyoung

4 6

Reverse traversing of xml.collected()?
by Gerben Wierda 10 Nov '20

10 Nov '20

I’d like to travese the contents of an xml.collected() in a reverse order. I have for connectionFromXML in xml.collected(viewFromXML,"/connection") do parseXMLConnection( rootFromXML, connectionFromXML, viewFromXML, rootFromOverrideXML) end I tried: local relationTable = xml.collected(viewFromXML,"/connection") for i=#relationTable, 1, -1 do connectionFromXML = relationTable[i] parseXMLConnection( rootFromXML, connectionFromXML, viewFromXML, rootFromOverrideXML) end But apparently my lua knowledge is lacking (severely, I might say) as this ends with “attempt to get length of a function value “ What is the correct way to do it? G

3 3

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

handle_error_hook in LuaMetaTeX
by Marcel Fabian Krüger 01 Aug '20

01 Aug '20

Hi, thanks for handling f file consition in LuaMetaTeX. While playing with that, I encountered a potential bug in the latest LuaMetaTeX version: If handle_error_hook is executed and returns any number, LuaMetaTeX segfaults. (I'm pretty sure that this still worked with the previous version) Minimal ConTeXt example: \enabledirectives[system.quitonerror=false] \directlua{ print(callbacks.register('handle_error_hook', function(...) return 3 end)) } \undefined % Trigger an error \starttext \stoptext This triggers [...] system > ConTeXt ver: 2020.07.31 10:20 LMTX fmt: 2020.7.31 int: english/english [...] tex error > tex error on line 7 in file ./test_empty_input.tex: ! Undefined control sequence l.7 \undefined [...] 9 \stoptext segmentation fault (core dumped) /home/marcel/lmtx-install/tex/texmf-linux-64/bin/luametatex cont-yes.mkiv valgrind suggests that this is caused by an attempt to access a null pointer: ==382632== Invalid write of size 4 ==382632== at 0x1A581F: ??? (in /home/marcel/lmtx-install/tex/texmf-linux-64/bin/luametatex) ==382632== by 0x1A662F: ??? (in /home/marcel/lmtx-install/tex/texmf-linux-64/bin/luametatex) ==382632== by 0x14BAA8: ??? (in /home/marcel/lmtx-install/tex/texmf-linux-64/bin/luametatex) ==382632== by 0x1DA50E: ??? (in /home/marcel/lmtx-install/tex/texmf-linux-64/bin/luametatex) ==382632== by 0x1DA802: ??? (in /home/marcel/lmtx-install/tex/texmf-linux-64/bin/luametatex) ==382632== by 0x15F956: ??? (in /home/marcel/lmtx-install/tex/texmf-linux-64/bin/luametatex) ==382632== by 0x156E2E: ??? (in /home/marcel/lmtx-install/tex/texmf-linux-64/bin/luametatex) ==382632== by 0x121E97: ??? (in /home/marcel/lmtx-install/tex/texmf-linux-64/bin/luametatex) ==382632== by 0x4A16001: (below main) (in /usr/lib/libc-2.31.so) ==382632== Address 0x0 is not stack'd, malloc'd or (recently) free'd ==382632== ==382632== ==382632== Process terminating with default action of signal 11 (SIGSEGV): dumping core ==382632== Access not within mapped region at address 0x0 ==382632== at 0x1A581F: ??? (in /home/marcel/lmtx-install/tex/texmf-linux-64/bin/luametatex) ==382632== by 0x1A662F: ??? (in /home/marcel/lmtx-install/tex/texmf-linux-64/bin/luametatex) ==382632== by 0x14BAA8: ??? (in /home/marcel/lmtx-install/tex/texmf-linux-64/bin/luametatex) ==382632== by 0x1DA50E: ??? (in /home/marcel/lmtx-install/tex/texmf-linux-64/bin/luametatex) ==382632== by 0x1DA802: ??? (in /home/marcel/lmtx-install/tex/texmf-linux-64/bin/luametatex) ==382632== by 0x15F956: ??? (in /home/marcel/lmtx-install/tex/texmf-linux-64/bin/luametatex) ==382632== by 0x156E2E: ??? (in /home/marcel/lmtx-install/tex/texmf-linux-64/bin/luametatex) ==382632== by 0x121E97: ??? (in /home/marcel/lmtx-install/tex/texmf-linux-64/bin/luametatex) ==382632== by 0x4A16001: (below main) (in /usr/lib/libc-2.31.so) That me know if you are interested in the coredump. Best regards, Marcel

2 1